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

From Christoph Berg
Subject Re: Set log_lock_waits=on by default
Date
Msg-id ZpppCLK1gNs7aXQS@msg.df7cb.de
Whole thread Raw
In response to Re: Set log_lock_waits=on by default  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: Set log_lock_waits=on by default
List pgsql-hackers
Re: Laurenz Albe
> 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.

That would be a pity, I still think log_lock_waits=on by default would
be a good thing.

I have not seen any server yet where normal, legitimate operation
would routinely trigger the message. (If it did, people should likely
have used SKIP LOCKED or NOWAIT instead.) It would only increase the
log volume on systems that have a problem.

Christoph



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [BUG] Fix DETACH with FK pointing to a partitioned table fails
Next
From: Tomas Vondra
Date:
Subject: Re: walsender.c fileheader comment