Solved! Go to Solution.
Hey @despainj83
Don't know enough yet about PostgreSQL but that error code seems to be tied to dynamic vs plain queries here: https://bobcares.com/blog/postgresql-error-42601/#:~:text=PostgreSQL%20error%2042601%20also%20occurs....
The same point made here:
https://stackoverflow.com/questions/16291944/postgresql-sql-state-42601-syntax-error
Hope this helps!
Hi @despainj83
Your Database team is correct, this is a Postgres version issue.
I dug through their documentation and it looks like they changed the syntax for the COPY command slightly and they added parameters. The ENCODING parameter we have in our commend wasn't added until version 9.1 of postgres.
I'm not sure what you can do besides upgrade.....
Release Notes: https://www.postgresql.org/docs/release/9.1.0/
E.76.3.5.1. COPY
Add ENCODING option to COPY TO/FROM (Hitoshi Harada, Itagaki Takahiro)
This allows the encoding of the COPY file to be specified separately from client encoding.
Add bidirectional COPY protocol support (Fujii Masao)
This is currently only used by streaming replication.
Welcome to Pirai Infotech, where innovation converges with transformation. As a premier digital solutions company, we specialize in shaping the future of businesses through cutting-edge technologies and strategic insights. Our Google Cloud Computing Services, designed to accelerate your journey towards digital innovation, enable you to swiftly prototype and launch your product idea. This allows you to gather valuable feedback and iterate efficiently. With Pirai Infotech as your trusted partner, you can confidently leverage Google Cloud Computing Services to navigate the complexities of digital transformation and unlock new opportunities for growth. Discover the possibilities with Pirai Infotech – your trusted partner for innovative and sustainable digital transformation.