avamingli commented on issue #928: URL: https://github.com/apache/cloudberry/issues/928#issuecomment-2667660888
> > > to recreate, just run `psql -f problem_ddl_cloudberry.sql` and then `psql -f problem_query.sql` > > > > > > Hi, i got error with the DDL file: > > ``` > > psql:problem_ddl_cloudberry.sql:32295: error: invalid command \N > > psql:problem_ddl_cloudberry.sql:32296: error: invalid command \N > > psql:problem_ddl_cloudberry.sql:32297: error: invalid command \N > > psql:problem_ddl_cloudberry.sql:32298: error: invalid command \N > > psql:problem_ddl_cloudberry.sql:32299: error: invalid command \N > > psql:problem_ddl_cloudberry.sql:32300: error: invalid command \N > > psql:problem_ddl_cloudberry.sql:32301: error: invalid command \. > > psql:problem_ddl_cloudberry.sql:32303: ERROR: syntax error at or near "33179" > > LINE 1: 33179 43627 197917 1 2024-11-24 10:20:53.129679 419 6 129600... > > ^ > > psql:problem_ddl_cloudberry.sql:41154: error: invalid command \. > > psql:problem_ddl_cloudberry.sql:41158: ERROR: syntax error at or near "38172" > > ``` > > > > > > > > > > > > > > > > > > > > > > > > Did you have other settings using pg_dump or sth else? exec to see the detailed version info. > > select version(); > > I removed the \N but still got error at several lines: > > psql:problem_ddl_cloudberry.sql:72: ERROR: invalid input syntax for type integer: "" > CONTEXT: COPY t1, line 6, column col9: "" > psql:problem_ddl_cloudberry.sql:32304: ERROR: invalid input syntax for type integer: "" > CONTEXT: COPY t2, line 3, column col9: "" > COPY 8850 > ALTER TABLE > But return zero data according the reproduce sql: > > col1 | col2 | col3 | col4 | col8 | unid | island_start | rn > ------+------+------+------+------+------+--------------+---- > (0 rows) > both for ORCA and Postgres planner. The data you provided doesn't match your schema, ex: t1 has 15 columns, but DDL form stdin only has 11 columns. ```sql COPY antonio.t1 FROM stdin; 34160 74264 275296 1 2171 02c2f5e4-7dd6-4f64-826b-3689e30383f6 2024-07-22 04:12:18.72691 2024-11-24 14:17:59.661649 2 2592000 1 180 34160 74264 284868 1 30 02c2f5e4-7dd6-4f64-826b-3689e30383f6 2024-08-19 21:18:26.81898 2024-11-24 14:17:59.790941 12 259200 1 180 34160 74264 275297 1 1800 02c2f5e4-7dd6-4f64-826b-3689e30383f6 2024-07-22 04:12:18.778009 2024-11-24 14:17:59.731069 1 43200 1 180 33416 66370 251452 1 2236 551da01e-d8e9-476c-b913-f96300667e85 2024-04-01 04:09:16.217534 2024-11-24 16:06:17.591228 2 2592000 1 180 33416 66370 251453 1 180 551da01e-d8e9-476c-b913-f96300667e85 2024-04-01 04:09:16.239326 2024-11-24 16:06:17.667193 1 43200 1 180 34160 74264 284869 1 2592000 02c2f5e4-7dd6-4f64-826b-3689e30383f6 2024-08-19 21:18:26.840662 2024-11-24 14:17:59.848033 2 2592000 1 180 \. ``` @antoniopetrole Hi, I could help you if there is a easy way to produce on main branch. 1. Could you provide an reproduce SQL on main branch 2. ```sql select version()``` 3. explain(verbose) show the plan of your unexpected results -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
