Re: removal of dangling temp tables - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: removal of dangling temp tables
Date
Msg-id 20181215034203.GF5012@paquier.xyz
Whole thread Raw
In response to Re: removal of dangling temp tables  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: removal of dangling temp tables  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Fri, Dec 14, 2018 at 11:06:32PM -0300, Alvaro Herrera wrote:
> I did propose in my OP the idea of a PGPROC boolean flag that indicates
> whether the temp namespace has been set up.  If not, have autovac remove
> those tables.  I like this option better, but I fear it adds more
> ProcArrayLock contention.  Maybe I can just use a new LWLock to
> coordinate that particular member of the ProcGlobal array ... (but then
> it can no longer be a boolean.)

Isn't that what tempNamespaceId can be used for in PGPROC now?  The flag
would be set only when a backend creates a new temporary schema so as it
can be tracked as the owner of the schema.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: New function pg_stat_statements_reset_query() to reset statisticsof a specific query
Next
From: Amit Kapila
Date:
Subject: unnecessary creation of FSM files during bootstrap mode