| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Cc: | John Naylor <johncnaylorls(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Can we remove support for standard_conforming_strings = off yet? |
| Date: | 2026-01-21 20:09:30 |
| Message-ID: | 2402302.1769026170@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Julien Rouhaud <rjuju123(at)gmail(dot)com> writes:
> On Tue, Jan 20, 2026 at 01:31:53PM -0500, Tom Lane wrote:
>> So, nobody's actually spoken against this change. I think we should
>> go forward with it, for the reasons I gave at the top of the thread
>> and because "if not now, when?". I have little doubt that if there
>> is anyone still running with standard_conforming_strings = off, they
>> aren't going to change until forced to. So unless we want to live
>> with the potential security hazard forever, we're going to have to
>> make a breaking change sometime.
> +1 from me. All of that is sensible, plus from an extension point of view it's
> easy to write code that is broken with standard_conforming_strings = off so
> it's one less thing to worry about.
Pushed.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2026-01-21 20:23:51 | Re: refactor architecture-specific popcount code |
| Previous Message | Viktor Holmberg | 2026-01-21 20:05:18 | Re: ON CONFLICT DO SELECT (take 3) |