From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Signaling of waiting for a cleanup lock? |
Date: | 2014-04-12 21:40:34 |
Message-ID: | CA+TgmoZDOrFWydOe_ENwmFaRTUAr9+Wq0Kfa6CH3M7=BDw8xzA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Apr 11, 2014 at 10:28 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> VACUUM sometimes waits synchronously for a cleanup lock on a heap
> page. Sometimes for a long time. Without reporting it externally.
> Rather confusing ;).
>
> Since we only take cleanup locks around vacuum, how about we report at
> least in pgstat that we're waiting? At the moment, there's really no way
> to know if that's what's happening.
That seems like a pretty good idea to me. I think we've avoided doing
this for LWLocks for fear that there might be too much overhead, but
it's hard for me to imagine a workload where you're waiting for
cleanup locks often enough for the overhead to matter.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | John Mudd | 2014-04-13 03:40:34 | Debug strategy for musl Postgres? |
Previous Message | Tom Lane | 2014-04-12 20:35:48 | Re: test failure on latest source |