Re: Displaying accumulated autovacuum cost - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Displaying accumulated autovacuum cost
Date
Msg-id CA+TgmoadM7k8scsW4t_LzLLaRGy79NckaX4+jXrWX_BjB7jOqw@mail.gmail.com
Whole thread Raw
In response to Re: Displaying accumulated autovacuum cost  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Displaying accumulated autovacuum cost
Re: Displaying accumulated autovacuum cost
List pgsql-hackers
On Fri, Nov 25, 2011 at 11:39 AM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
> I'm going to push this now anyway, thanks.

This patch adds a count of the number of buffers dirtied to VACUUM,
but it strikes me that it would be useful to add similar tracking to
pgBufferUsage.  Attached is a patch for that.  You can see the new
counters through pg_stat_statements or with EXPLAIN (ANALYZE,
BUFFERS).  This is useful because the number of buffers that a query
*writes* doesn't necessarily have much to do with anything - it may
end up writing buffers dirtied by other queries while being read-only
itself, or conversely it may not write anything at all even though it
dirties quite a bit.

Thoughts?  Comments?  Objections?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attachment

pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Re: Measuring relation free space
Next
From: Jaime Casanova
Date:
Subject: Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID