Re: identifying the backend that owns a temporary schema
Nathan Bossart <nathandbossart@gmail.com>
From: Nathan Bossart <nathandbossart@gmail.com>
To: Greg Stark <stark@mit.edu>
Cc: pgsql-hackers@postgresql.org
Date: 2022-08-29T23:07:57Z
Lists: pgsql-hackers
On Tue, Aug 23, 2022 at 10:29:05AM +0100, Greg Stark wrote: > Having this function would be great (I admit I never responded because > I never figured out if your suggestion was right or not:). But should > it also be added to the pg_stat_activity view? Perhaps even just in > the SQL view using the function. > > Alternately should pg_stat_activity show the actual temp schema name > instead of the id? I don't recall if it's visible outside the backend > but if it is, could pg_stat_activity show whether the temp schema is > actually attached or not? I'm open to adding the backend ID or the temp schema name to pg_stat_activity, but I wouldn't be surprised to learn that others aren't. It'd be great to hear a few more opinions on the idea before I spend too much time on the patches. IMO we should still adjust the pg_stat_get_backend_*() functions even if we do end up adjusting pg_stat_activity. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com
Commits
-
Use actual backend IDs in pg_stat_get_backend_idset() and friends.
- d7e39d72ca1c 16.0 landed