| From: | Michael Banck <mbanck(at)gmx(dot)net> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Set log_lock_waits=on by default |
| Date: | 2024-01-24 17:19:53 |
| Message-ID: | 65b146b9.170a0220.c645b.0891@mx.google.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Thu, Jan 11, 2024 at 03:24:55PM +0100, Michael Banck wrote:
> On Thu, Dec 21, 2023 at 02:29:05PM +0100, Laurenz Albe wrote:
> > Here is a patch to implement this.
> > Being stuck behind a lock for more than a second is almost
> > always a problem, so it is reasonable to turn this on by default.
>
> I also think that this should be set to on.
>
> I had a look at the patch and it works fine.
>
> Regarding the documentation, maybe the back-reference at
> deadlock_timeout could be made a bit more explicit then as well, as in
> the attached patch, but this is mostly bikeshedding.
I've marked it ready for committer now, as the above really is
bikeshedding.
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-01-24 17:23:24 | Re: Add system identifier to backup manifest |
| Previous Message | Nathan Bossart | 2024-01-24 17:08:46 | Re: cleanup patches for incremental backup |