| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Do quoting more carefully in replication commands |
| Date: | 2026-06-12 21:24:05 |
| Message-ID: | 1660526.1781299445@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
=?utf-8?Q?=C3=81lvaro?= Herrera <alvherre(at)kurilemu(dot)de> writes:
> In a quick skim, I wondered about this bit:
>> + * Caution: this quoting logic is sufficient for identifiers and literals
>> + * in the replication grammar, but not always in regular SQL. Specifically,
>> + * it'd fail for a string literal if standard_conforming_strings is off.
> ... given that standard_conforming_strings can no longer be off in 19.
> The backpatched version should surely still have this, just in case, but
> in 19 it's probably not needed.
There are assorted places in the backend that want to generate SQL
that will work against older versions. I don't think we can forget
about standard_conforming_strings until all those versions are off
even the support-back-to list, ie about 10 years from now.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Previous Message | Álvaro Herrera | 2026-06-12 21:02:05 | Re: Do quoting more carefully in replication commands |