From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Which backend using which pg_temp_N schema? |
Date: | 2018-06-06 16:11:57 |
Message-ID: | 11089.1528301517@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Jerry Sievers <gsievers19(at)comcast(dot)net> writes:
> Yep thanks... but IMO something that simply exposes whatever internal
> registry of temp schemas/PIDs (which I presume must exist)
Not really. There are a couple of ways that one could identify a
session's "BackendId", which is the "N" in the "pg_temp_N" name of
the temp schema that it would use if it uses one. But I do not think
there's any terribly reliable way to tell from outside the session
whether it has actually done anything with the temp schema. If it
hasn't, then at least in principle there could be objects in the
schema that are left over from a crashed session that previously had
the same BackendId. We only make an effort to clean out such objects
at the time that a session first creates a temp object.
In any case, I think you're right that this isn't exposed at the SQL
level presently.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jeremy Finzel | 2018-06-06 16:59:23 | Slow planning time for simple query |
Previous Message | Jerry Sievers | 2018-06-06 15:54:40 | Re: Which backend using which pg_temp_N schema? |