Re: pg_shmem_allocations view
Andres Freund <andres@2ndquadrant.com>
From: Andres Freund <andres@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, Marti Raudsepp <marti@juffo.org>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2014-08-18T17:36:31Z
Lists: pgsql-hackers
On 2014-08-18 13:27:07 -0400, Tom Lane wrote: > 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. That might be true in some cases, but in many cases interfaces that can only be used via gdb *SUCK*. A good reason to use the interface proposed here is to investigate which extensions are allocating how much shared memory. A pretty normal question to ask as a sysadmin/DBA. And DBA type of stuff should never have to involve gdb. 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