Re: pg_shmem_allocations view - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: pg_shmem_allocations view
Date
Msg-id CAB7nPqTFj9hck09iQ_1c+=dvPkYerVEViuHPtAoP-9OH4=Dqnw@mail.gmail.com
Whole thread Raw
In response to Re: pg_shmem_allocations view  (Andres Freund <andres@anarazel.de>)
List 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



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: pg9.6 segfault using simple query (related to use fk for join estimates)
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Re: [HACKERS] Re: [HACKERS] Re: [HACKERS] Windows service is not starting so there’s message in log: FATAL: "could not create shared memory segment “Global/PostgreSQL.851401618”: Permission denied”