Hello Tom and Adrian > -----Original Message----- > From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-owner@xxxxxxxxxxxxxx] On Behalf Of Adrian Klaver > Sent: Sonntag, 25. September 2016 18:38 > To: Tom Lane <tgl@xxxxxxxxxxxxx>; Charles Clavadetscher <clavadetscher@xxxxxxxxxxxx> > Cc: pgsql-general@xxxxxxxxxxxxxx > Subject: Re: Question on replace function [solved] > > On 09/25/2016 08:39 AM, Tom Lane wrote: > > Charles Clavadetscher <clavadetscher@xxxxxxxxxxxx> writes: > >> Honestly I still don't understand why this happened this way. > > > > I wonder if you have standard_conforming_strings turned off, or did > > when that data was inserted. That would change the behavior of > > backslashes in string literals. > > That got me to thinking: > > standard_conforming_strings = on I checked the configuration and standard_conforming_strings is on and I did not change it before reading the data. The result looks the same as you showed in the first test. In a short test, trying to read the file with this setting off leads to other errors. Possibly I'll be able to make some more tests later or in the evening and report. Thank you for you input. Charles -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
