MIME-Version: 1.0
References: <CANzqJaD0=V+Dh+mLLfLj4ECLHriAH122LiYaqKyAnWCAKCfa6A@mail.gmail.com>
 <CAKFQuwbdAm7=RziKxF+jQki0KXb-quan5fA3sfq8JKoDR3Jumw@mail.gmail.com>
 <CANzqJaCL_p2LmCAUPGUYxOJPN-iOs-JWbpU4ssH+rSw27DmvhA@mail.gmail.com>
 <CAKFQuwZhOgbn+wbDTRXyqON2AEJM-R_Na2yHjLD0r9V4a+Fx=Q@mail.gmail.com>
 <CANzqJaDTY0AEB2zxumCbDtZu_pVxcjWpf5FdSeGwShLM3SfVzg@mail.gmail.com> <730017.1718032111@sss.pgh.pa.us>
In-Reply-To: <730017.1718032111@sss.pgh.pa.us>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Mon, 10 Jun 2024 11:19:32 -0400
Message-ID: <CANzqJaDqZtWfk=s1_886m7TzTMek87Qcefpns4WRBvjm-9f-_w@mail.gmail.com>
Subject: Re: Escaping single quotes with backslash seems not to work
To: pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000d3504b061a8aad93"
Archived-At: <https://www.postgresql.org/message-id/CANzqJaDqZtWfk%3Ds1_886m7TzTMek87Qcefpns4WRBvjm-9f-_w%40mail.gmail.com>
Precedence: bulk

--000000000000d3504b061a8aad93
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 10, 2024 at 11:08=E2=80=AFAM Tom Lane <tgl@sss.pgh.pa.us> wrote=
:

> Ron Johnson <ronljohnsonjr@gmail.com> writes:
> > On Mon, Jun 10, 2024 at 10:56=E2=80=AFAM 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 configure=
d
> 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 =3D on" is at the top, and there's no other
reference to it.

--000000000000d3504b061a8aad93
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Jun 10, 2024 at 11:08=E2=80=AFAM =
Tom Lane &lt;<a href=3D"mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>&gt;=
 wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex">Ron Johnson &lt;<a href=3D"mailto:ronljohnsonjr@gmail.co=
m" target=3D"_blank">ronljohnsonjr@gmail.com</a>&gt; writes:<br>
&gt; On Mon, Jun 10, 2024 at 10:56=E2=80=AFAM David G. Johnston &lt;<br>
&gt; <a href=3D"mailto:david.g.johnston@gmail.com" target=3D"_blank">david.=
g.johnston@gmail.com</a>&gt; wrote:<br>
&gt;&gt; As the caution on that page says the default for standard conformi=
ng<br>
&gt;&gt; strings changed in 9.1. But maybe your 9.6 had the old value confi=
gured but<br>
&gt;&gt; when you upgraded to 14 you decided to go with the new default.<br=
>
<br>
&gt; That was the first thing I checked... It&#39;s the same on both the 9.=
6 and 14<br>
&gt; systems:.<br>
<br>
Did you check that as the user that runs the Java app (I sure hope<br>
it&#39;s not the superuser you evidently used here), in the DB the Java<br>
app uses?=C2=A0 I&#39;m wondering about per-user or per-DB settings of<br>
standard_conforming_strings.<br></blockquote><div><br></div><div>It&#39;s a=
 remote Java app which runs as a non-superuser.=C2=A0 I don&#39;t know what=
 it&#39;s doing.</div><div><br></div><div>I ran &quot;pg_dumpuser -g&quot; =
on the old systems, and applied=C2=A0the sql to the corresponding new serve=
rs.=C2=A0=C2=A0</div><div><br></div><div>&quot;set standard_encoding_string=
s =3D on&quot; is at the top, and there&#39;s no other reference to it.</di=
v><div><br></div></div></div>

--000000000000d3504b061a8aad93--