Re: Schema variables - new implementation for Postgres 15 - Mailing list pgsql-hackers

From Julien Rouhaud
Subject Re: Schema variables - new implementation for Postgres 15
Date
Msg-id CAOBaU_YM2sq6A9KK-bDcp6=RDLvjtpMJb4egW0f8pq0X2-62Yw@mail.gmail.com
Whole thread Raw
In response to Re: Schema variables - new implementation for Postgres 15  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On Thu, Apr 6, 2023 at 1:58 AM Pavel Stehule <pavel.stehule@gmail.com> wrote:
>
> st 5. 4. 2023 v 19:20 odesílatel Greg Stark <stark@mit.edu> napsal:
>>
>> On Sun, 26 Mar 2023 at 07:34, Julien Rouhaud <rjuju123@gmail.com> wrote:
>> >
>> > This feature can significantly increase log size, so it's disabled by default.
>> > For testing or development environments it's recommended to enable it if you
>> > use session variables.
>>
>> I think it's generally not practical to have warnings for valid DML.
>> Effectively warnings in DML are errors since they make the syntax just
>> unusable. I suppose it's feasible to have it as a debugging option
>> that defaults to off but I'm not sure it's really useful.
>
>
> It is a tool that should help with collision detection.  Without it, it can be pretty hard to detect it. It is
similarto plpgsql's extra warnings. 

Another example is escape_string_warning, which can also emit warning
for valid DML.  I once had to fix some random framework that a
previous employer was using, in order to move to a more recent pg
version and have standard_conforming_strings on, and having
escape_string_warning was quite helpful.



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: zstd compression for pg_dump
Next
From: Melanie Plageman
Date:
Subject: Re: Should vacuum process config file reload more often