From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Add the number of pinning backends to pg_buffercache's output |
Date: | 2014-04-12 12:25:01 |
Message-ID: | 20140412122501.GS14419@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
The last week I twice had the need to see how many backends had some
buffers pinned. Once during development and once while analyzing a stuck
vacuum (waiting for a cleanup lock).
I'd like to add a column to pg_buffercache exposing that. The name I've
come up with is 'pinning_backends' to reflect the fact that it's not the
actual pincount due to the backend private arrays.
I'll add this patch to to 2014-06 CF.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
Attachment | Content-Type | Size |
---|---|---|
0001-Add-pinning_backends-column-to-the-pg_buffercache-ex.patch | text/x-patch | 8.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2014-04-12 12:34:49 | Re: Problem with txid_snapshot_in/out() functionality |
Previous Message | MauMau | 2014-04-12 07:51:25 | Re: [bug fix] pg_ctl always uses the same event source |