Re: Autovaccuum vs temp tables crash

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Autovaccuum vs temp tables crash
Date: 2019-02-22 18:14:35
Message-ID: 18143.1550859275@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Fri, Feb 22, 2019 at 12:54 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>>> On Fri, Feb 22, 2019 at 3:43 AM Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>>>> We are certainly not supposed to go DROP SCHEMA on the temp namespaces, ...

>>> Actually, I think that's supposed to work.

>> If it's in active use by any session (including your own), that's not going
>> to have nice consequences; the owning session will have the OID in
>> static storage, and it will be unhappy when that OID becomes dangling.

> Maybe that's something we should fix?

Why? It would likely be a significant amount of effort and added overhead,
to accomplish no obviously-useful goal.

Note that all the temp schemas are made as owned by the bootstrap
superuser, so there is no real argument to be made that people might
be expecting they should be able to delete them.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2019-02-22 18:15:35 Re: Autovaccuum vs temp tables crash
Previous Message Corey Huinker 2019-02-22 18:12:42 Re: some ri_triggers.c cleanup