[NEOS-1799] Tables with one column break jobs
buglinear
A table with a single column (with PK constraint, in my case) causes export to hang.
On inspecting the worker docker container, the error logged repeatedly is:
```
{"time":"2025-03-28T16:56:27.700158258Z","level":"ERROR","msg":"Failed to send message to error: failed to build insert query: failed to build postgres insert query: goqu: no update values provided\n","ActivityID":"5","ActivityType":"SyncTable","Attempt":1,"JobRunId":"cdb9a420-3682-49f9-9382-c257abb59049-2025-03-28T16:53:37Z","Namespace":"default","RunID":"2413ba57-4062-4222-95ab-cc01aae6d48f","TaskQueue":"sync-job","WorkerID":"1@db76fceabb15@","WorkflowID":"cdb9a420-3682-49f9-9382-c257abb59049-2025-03-28T16:53:37Z-public_test_table_single_col_insert-1743180817570433554","WorkflowType":"TableSync","accountId":"43c71652-b3f7-4dbb-87c2-508075496054","activitySession":"cdb9a420-3682-49f9-9382-c257abb59049-2025-03-28T16:53:37Z:6feb69ba-ffe0-4c45-bc50-9875968b33d6","benthos":"true","hasContinuationToken":false,"id":"public.test_table_single_col.insert","label":"","metadata":{"Schema":"public","Table":"test_table_single_col"},"path":"root.output.broker.outputs.0.fallback.1"}
```
This results in jobs running forever and eventually timing out.
## How to reproduce
```
CREATE TABLE test_table_single_col (
name TEXT PRIMARY KEY
);
INSERT INTO test_table_single_col (name) VALUES ('TEST_VAL');
```
## Environment
MacOS / docker
## Additional context
I have tried tweaking some settings, such as batch sizes and schema initialization inside vs. already done prior - nothing causes any change.
#### *Thank you* for your bug report – we love squashing them!
<sub>[NEOS-1799](https://linear.app/nucleus-cloud/issue/NEOS-1799/tables-with-one-column-break-jobs)</sub>
关闭于 2025-03-28 3 条评论