Re: pg_shmem_allocations view

Andres Freund <andres@2ndquadrant.com>

From: Andres Freund <andres@2ndquadrant.com>
To: Marti Raudsepp <marti@juffo.org>
Cc: Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2014-08-15T08:20:35Z
Lists: pgsql-hackers
On 2014-08-15 11:12:11 +0300, Marti Raudsepp wrote:
> Hi
> 
> On Thu, May 8, 2014 at 4:28 PM, Andres Freund <andres@2ndquadrant.com> wrote:
> > Ok. A new version of the patches implementing that are
> > attached. Including a couple of small fixups and docs. The latter aren't
> > extensive, but that doesn't seem to be warranted anyway.
> 
> Is it really actually useful to expose the segment off(set) to users?
> Seems to me like unnecessary internal details leaking out.

Yes. This is clearly developer oriented and I'd more than once wished I
could see where some stray pointer is pointing to... That's not really
possible without something like this.

Greetings,

Andres Freund

-- 
 Andres Freund	                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


Commits

  1. Add pg_shmem_allocations view.