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

From Robert Haas
Subject Re: removal of dangling temp tables
Date
Msg-id CA+TgmoYdgL7pRBAkucZoZriVExJvS+TqGZ7yZNF0roi7FiHwLA@mail.gmail.com
Whole thread Raw
In response to removal of dangling temp tables  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: removal of dangling temp tables  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: removal of dangling temp tables  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Dec 14, 2018 at 11:29 AM Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> I think the best way to fix this is to call RemoveTempRelations()
> unconditionally at session start (without doing the rest of the temp
> table setup, just the removal.)

That would certainly simplify things.  I think I thought about that as
far back as a734fd5d1c309cc553b7c8c79fba96218af090f7 but it seemed
like a significant behavior change and I wasn't sure that everyone
would like it.  In particular, it adds overhead to backend startup
that, in the case of a large temp schema, could be fairly long.

Nevertheless, I tentatively think that a change like this is a good
idea.  I wouldn't back-patch it, though.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Gajus Kuizinas
Date:
Subject: A case for UPDATE DISTINCT attribute
Next
From: Alvaro Herrera
Date:
Subject: Re: fix psql \conninfo & \connect when using hostaddr