From: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
---|---|
To: | Greg Stark <stark(at)mit(dot)edu> |
Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: identifying the backend that owns a temporary schema |
Date: | 2022-08-23 11:30:57 |
Message-ID: | CAMsGm5cPjXbk+-15vrc6yjZoSUj6egcUeHZTK5sey9RHcHDooQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 23 Aug 2022 at 05:29, Greg Stark <stark(at)mit(dot)edu> 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?
>
Would it work to cast the schema oid to type regnamespace? Then the actual
data (numeric oid) would be present in the view, but it would display as
text.
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2022-08-23 12:07:05 | Re: Tracking last scan time |
Previous Message | Dilip Kumar | 2022-08-23 09:58:25 | Re: making relfilenodes 56 bits |