Re: Escaping single quotes with backslash seems not to work - Mailing list pgsql-general

From Ron Johnson
Subject Re: Escaping single quotes with backslash seems not to work
Date
Msg-id CANzqJaDqZtWfk=s1_886m7TzTMek87Qcefpns4WRBvjm-9f-_w@mail.gmail.com
Whole thread Raw
In response to Re: Escaping single quotes with backslash seems not to work  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Escaping single quotes with backslash seems not to work
List pgsql-general
On Mon, Jun 10, 2024 at 11:08 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Ron Johnson <ronljohnsonjr@gmail.com> writes:
> On Mon, Jun 10, 2024 at 10:56 AM David G. Johnston <
> david.g.johnston@gmail.com> wrote:
>> As the caution on that page says the default for standard conforming
>> strings changed in 9.1. But maybe your 9.6 had the old value configured but
>> when you upgraded to 14 you decided to go with the new default.

> That was the first thing I checked... It's the same on both the 9.6 and 14
> systems:.

Did you check that as the user that runs the Java app (I sure hope
it's not the superuser you evidently used here), in the DB the Java
app uses?  I'm wondering about per-user or per-DB settings of
standard_conforming_strings.

It's a remote Java app which runs as a non-superuser.  I don't know what it's doing.

I ran "pg_dumpuser -g" on the old systems, and applied the sql to the corresponding new servers.  

"set standard_encoding_strings = on" is at the top, and there's no other reference to it.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Escaping single quotes with backslash seems not to work
Next
From: Adrian Klaver
Date:
Subject: Re: Escaping single quotes with backslash seems not to work