Re: Set log_lock_waits=on by default

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Michael Banck <mbanck(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Set log_lock_waits=on by default
Date: 2025-04-08 14:32:49
Message-ID: a459b7d045775784617897592632a6eade915def.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 2024-07-19 at 11:54 +0200, Laurenz Albe 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.

Well, it didn't make v18.

But this patch got enough votes in favor that I am not going to withdraw it.

Yours,
Laurenz Albe

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2025-04-08 14:36:45 Feature freeze
Previous Message Bruce Momjian 2025-04-08 14:32:21 Re: [PoC] Federated Authn/z with OAUTHBEARER