Re: Set log_lock_waits=on by default - Mailing list pgsql-hackers

From Jelte Fennema-Nio
Subject Re: Set log_lock_waits=on by default
Date
Msg-id CAGECzQQTCMqDLJA9RcVn=R03+_NTNTrQ+2qxzmTMA+SPOBFdjw@mail.gmail.com
Whole thread Raw
In response to Re: Set log_lock_waits=on by default  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-hackers
Late to the party, but +1 from me on this default change also

On Fri, 19 Jul 2024 at 11:54, Laurenz Albe <laurenz.albe@cybertec.at> wrote:
On Thu, 2024-07-18 at 12:25 +0200, Michael Banck wrote:
> this patch is still on the table, though for v18 now.
>
> Nathan mentioned up-thread that he was hesitant to commit this without
> further discussion. Laurenz, Stephen and I are +1 on this, but when it
> comes to committers having chimed in only Tom did so far and was -1.
>
> Are there any others who have an opinion on this?

If we want to tally up, there were also +1 votes from Christoph Berg,
Shinya Kato, Nikolay Samokhvalov, Jeremy Schneider and Frédéric Yhuel.

The major criticism is Tom's that it might unduly increase the log volume.

I'm not trying to rush things, but I see little point in kicking a trivial
patch like this through many commitfests.  If no committer wants to step
up and commit this, it should be rejected.

Yours,
Laurenz Albe


pgsql-hackers by date:

Previous
From: Greg Sabino Mullane
Date:
Subject: Re: Set log_lock_waits=on by default
Next
From: "David G. Johnston"
Date:
Subject: Re: behavior of GROUP BY with VOLATILE expressions