| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Baji Shaik <baji(dot)pgdev(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] Doc: document standard_conforming_strings dump/restore incompatibility |
| Date: | 2026-06-18 15:34:46 |
| Message-ID: | 1242905.1781796886@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Wed, Jun 17, 2026 at 01:29:09PM -0400, Tom Lane wrote:
>> I'm inclined to do more or less the attached, which also fixes what
>> seems a thinko in the existing text: we should say that clients still
>> support standard_conforming_strings = off, not
>> escape_string_warning = off.
> I have applied a slightly modified version to master, attached. The git
> commit suggested this problem, but I didn't understand the impact at the
> time I read it.
This didn't correct the point I complained of above: it still says
Client applications still support <literal>escape_string_warning = off</literal> for compatibility with old servers.
The notion of a client "supporting" escape_string_warning seems quite
meaningless. I think this intended to say standard_conforming_strings =
off.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2026-06-18 15:36:06 | Fix publisher-side sequence permission reporting |
| Previous Message | Florin Irion | 2026-06-18 15:34:03 | Re: Fix HAVING-to-WHERE pushdown with mismatched operator families |