Preset Feature Feedback
What is the problem or goal the end user is trying to solve or accomplish?
A customer is trying to upload a CSV file to an Amazon Redshift Serverless cluster using Preset’s “Upload CSV to Database” feature. The process consistently takes over 10 minutes and eventually fails due to the Redshift statement_timeout. The goal is to successfully upload CSVs to Redshift through the UI without hitting performance or timeout issues.
How are they solving it currently?
They switched to using DataGrip to upload the same CSV directly into Redshift. DataGrip batches rows into multi-row INSERT statements, completing the upload in ~3 minutes with no issues. This workaround confirms the problem lies in Preset’s current upload mechanism.
What is the recommended solution by the Customer?
The customer is open to improvements in the upload logic that would allow faster ingestion into Redshift. This could include:
Supporting Redshift’s native COPY command (e.g., upload to S3 and execute COPY)
Or at least performing larger batched INSERTs instead of row-by-row
This enhancement would allow Redshift users to reliably use Preset’s UI for uploading files and reduce dependence on external tools.
