Re: [GENERAL] encoding confusion with \copy command

2014-09-17 Thread Martin Waite
You are right that I need an intermediate step. I will probably use a CSV parser that is liberal in what it accepts, but writes out strict CSV data suitable for postgres. Thanks for the help. On 17 September 2014 15:40, Adrian Klaver wrote: > On 09/17/2014 06:48 AM, Martin Waite wr

Re: [GENERAL] encoding confusion with \copy command

2014-09-17 Thread Martin Waite
Hi Adrian, I apologise - I meant 9.4 regards, Martin On 17 September 2014 14:35, Adrian Klaver wrote: > On 09/17/2014 03:03 AM, Martin Waite wrote: > >> Hi, >> >> I have a postgresql 7.4 server and client on Centos 6.4. The database >> server is using UTF-8 enc

[GENERAL] encoding confusion with \copy command

2014-09-17 Thread Martin Waite
Hi, I have a postgresql 7.4 server and client on Centos 6.4. The database server is using UTF-8 encoding. I have been exploring the use of the \copy command for importing CSV data generated by SQL Server 2008. SQL Server 2008 export tool does not escape quotes that are in the content of fields,