| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_shmem_allocations view |
| Date: | 2014-05-08 13:28:22 |
| Message-ID: | 20140508132822.GK30324@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-05-08 07:58:34 -0400, Robert Haas wrote:
> On Wed, May 7, 2014 at 5:54 PM, Andres Freund <andres(at)2ndquadrant(dot)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
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Associate-names-to-created-dynamic-shared-memory-seg.patch | text/x-patch | 5.1 KB |
| 0002-Add-views-to-see-shared-memory-allocations.patch | text/x-patch | 15.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2014-05-08 13:32:13 | Re: [v9.5] Custom Plan API |
| Previous Message | Simon Riggs | 2014-05-08 13:26:38 | Re: [v9.5] Custom Plan API |