Re: pg_shmem_allocations view
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Andres Freund <andres@2ndquadrant.com>, Marti Raudsepp <marti@juffo.org>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2014-08-18T17:27:07Z
Lists: pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes: > I thought you were printing actual pointer addresses. If you're just > printing offsets relative to wherever the segment happens to be > mapped, I don't care about that. Well, that just means that it's not an *obvious* security risk. I still like the idea of providing something comparable to MemoryContextStats, rather than creating a SQL interface. The problem with a SQL interface is you can't interrogate it unless (1) you are not already inside a query and (2) the client is interactive and under your control. Something you can call easily from gdb is likely to be much more useful in practice. regards, tom lane
Commits
-
Add pg_shmem_allocations view.
- ed10f32e37e9 13.0 landed