Обсуждение: about psql copy ,we would like to seek help,Thanks.
PSQL engineers, hello:
We encountered a problem during the process of importing data from a text file to the PG database using psql's COPY command, and we would like to seek help. The issue is that if there are any exceptional records in the file, the program exits, but we want to skip those erroneous records and continue with the rest of the import.
We have looked at some tutorials, and it seems that we can use the "CONTINUE" option. By using the CONTINUE option, the COPY command should ignore error rows and continue with the copying operation until all rows are copied. The relevant error information for the error rows will be recorded.
COPY table_name FROM '/path/to/data/file.csv' (FORMAT csv, DELIMITER ',', NULL '', CONTINUE);
However, when we actually tried this, an error occurred, and it seems that the parameter is not recognized.
ERROR: option "continue" not recognized
My psql version : psql (PostgreSQL) 12.7
Could this be due to the version? Are there any other ways to handle this? Thank you for your support.
Best Regards.
Gaosheng
2023-12-14 from China
PSQL engineers, hello:
We encountered a problem during the process of importing data from a text file to the PG database using psql's COPY command, and we would like to seek help. The issue is that if there are any exceptional records in the file, the program exits, but we want to skip those erroneous records and continue with the rest of the import.
We have looked at some tutorials,
On Thu, Dec 14, 2023 at 09:04:55AM +0800, 高升 wrote: > We have looked at some tutorials, and it seems that we can use the > "CONTINUE" option. By using the CONTINUE option, the COPY command should > ignore error rows and continue with the copying operation until all rows are > copied. The relevant error information for the error rows will be recorded. I searched the web using google and duckduckgo, and the phrase "By using the CONTINUE option, the COPY command should" doesn't exist anywhere. Which suggests that it wasn't "some tutorial" but rather hallucination by chatgpt or some other "ai" that provides untruths. In future, I would suggest to verify the things that these things spew, as even 5 second glance at copy documentation https://www.postgresql.org/docs/current/sql-copy.html shows that there is no such option. depesz
> On Dec 14, 2023, at 00:08, hubert depesz lubaczewski <depesz@depesz.com> wrote: > Which suggests that it wasn't "some tutorial" but rather hallucination > by chatgpt or some other "ai" that provides untruths. Snowflake (for example) has a CONTINUE option on COPY, so it's possible either the OP pulled up a tutorial for a differentdatabase system, or the "author" of the tutorial smashed multiple different systems together.
Dear engineers, Thank you for your valuable input and suggestions. We appreciate your assistance and guidance in this matter. We are grateful for your support ,Thanks very much . Best regards, Gaosheng 2023-12-15 -----邮件原件----- 发件人: xof@thebuild.com [mailto:xof@thebuild.com] 发送时间: 2023年12月14日 16:15 收件人: depesz@depesz.com 抄送: 高升; pgsql-bugs@lists.postgresql.org 主题: Re: about psql copy ,we would like to seek help,Thanks. > On Dec 14, 2023, at 00:08, hubert depesz lubaczewski <depesz@depesz.com> wrote: > Which suggests that it wasn't "some tutorial" but rather hallucination > by chatgpt or some other "ai" that provides untruths. Snowflake (for example) has a CONTINUE option on COPY, so it's possible either the OP pulled up a tutorial for a different database system, or the "author" of the tutorial smashed multiple different systems together.