Re: pg_shmem_allocations view
Andres Freund <andres@2ndquadrant.com>
From: Andres Freund <andres@2ndquadrant.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2014-05-08T13:28:22Z
Lists: pgsql-hackers
Attachments
- 0001-Associate-names-to-created-dynamic-shared-memory-seg.patch (text/x-patch) patch 0001
- 0002-Add-views-to-see-shared-memory-allocations.patch (text/x-patch) patch 0002
On 2014-05-08 07:58:34 -0400, Robert Haas wrote: > On Wed, May 7, 2014 at 5:54 PM, Andres Freund <andres@2ndquadrant.com> wrote: > > Hm. Not sure what you're ACKing here ;). > > The idea of giving the unallocated memory a NULL key. 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. > > There's lots of allocations from shmem that cannot be associated with > > any index entry though. Not just ShmemIndex's own entry. Most > > prominently most of the memory used for SharedBufHash isn't actually > > associated with the "Shared Buffer Lookup Table" entry - imo a > > dynahash.c defficiency. > Hmm, I don't know what to do about that. Well, we have to live with it for now :) Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
Commits
-
Add pg_shmem_allocations view.
- ed10f32e37e9 13.0 landed