From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)2ndquadrant(dot)com>, Marti Raudsepp <marti(at)juffo(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_shmem_allocations view |
Date: | 2016-05-09 07:05:31 |
Message-ID: | CAB7nPqTFj9hck09iQ_1c+=dvPkYerVEViuHPtAoP-9OH4=Dqnw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, May 6, 2016 at 8:01 AM, Andres Freund <andres(at)anarazel(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2016-05-09 07:17:21 | 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” |
Previous Message | Simon Riggs | 2016-05-09 05:47:57 | Re: pg9.6 segfault using simple query (related to use fk for join estimates) |