Re: identifying the backend that owns a temporary schema - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: identifying the backend that owns a temporary schema
Date
Msg-id 20220829230757.GA542616@nathanxps13
Whole thread Raw
In response to Re: identifying the backend that owns a temporary schema  (Greg Stark <stark@mit.edu>)
Responses Re: identifying the backend that owns a temporary schema
List 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



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: archive modules
Next
From: Michael Paquier
Date:
Subject: Re: [PATCH] Add native windows on arm64 support