| 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-11 14:24:55 |
| Message-ID: | 659ffa38.170a0220.eea6a.28fc@mx.google.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
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.
Michael
| Attachment | Content-Type | Size |
|---|---|---|
| log-lock-waits-doc.patch | text/x-diff | 1.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2024-01-11 14:25:52 | Re: Assertion failure in SnapBuildInitialSnapshot() |
| Previous Message | vignesh C | 2024-01-11 14:20:46 | Re: odd buildfarm failure - "pg_ctl: control file appears to be corrupt" |