On Wed, Jun 17, 2020 at 11:56 PM Fujii Masao <masao.fu...@oss.nttdata.com> wrote: > > As a first step, to deal with (3) I'd like to add > > pg_stat_get_backend_memory_context() which target is limited to the > > local backend process. > > +1
+1 from me, too. Something that exposed this via shared memory would be quite useful, and there are other things we'd like to expose similarly, such as the plan(s) from the running queries, or even just the untruncated query string(s). I'd like to have a good infrastructure for that sort of thing, but I think it's quite tricky to do properly. You need a variable-size chunk of shared memory, so probably it has to use DSM somehow, and you need to update it as things change, but if you update it too frequently performance will stink. If you ping processes to do the updates, how do you know when they've completed them, and what happens if they don't respond in a timely fashion? These are probably all solvable problems, but I don't think they are very easy ones. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
