Re: pg_shmem_allocations view
Michael Paquier <michael.paquier@gmail.com>
From: Michael Paquier <michael.paquier@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@2ndquadrant.com>, Marti Raudsepp <marti@juffo.org>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2016-05-09T07:05:31Z
Lists: pgsql-hackers
On Fri, May 6, 2016 at 8:01 AM, Andres Freund <andres@anarazel.de> wrote: > Here's a rebased version. I remember why I didn't call the column > "offset" (as Michael complained about upthread), it's a keyword... Oh, an old patch resurrected from the dead... Reading again the patch + * Increase number of initilized slots if we didn't reuse a previously + * used one. s/initilized/initialized + Number of backends attached to this segment (1 signals a moribund + entry, 2 signals one user, ...). moribund? Or target for removal. REVOKE ALL .. FROM PUBLIC; REVOKE EXECUTE .. ON FUNCTION FROM PUBLIC; Revoking he execution of those views and their underlying functions would be a good thing I think, this can give hints on the system activity, particularly for DSM segments. -- Michael
Commits
-
Add pg_shmem_allocations view.
- ed10f32e37e9 13.0 landed