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

From Andres Freund
Subject Re: removal of dangling temp tables
Date
Msg-id 20181214184008.texevy73ajq6air6@alap3.anarazel.de
Whole thread Raw
In response to Re: removal of dangling temp tables  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi,

On 2018-12-14 13:35:50 -0500, Tom Lane wrote:
> Hm.  It *could*, if we wanted it to run some transactions after
> finishing recovery.

How, we don't have infrastructure for changing databases yet?


> But I guess I wonder why bother; if the disk
> space is gone then there's not that much reason to be in a hurry
> to get rid of the catalog entries.  The particular problem Alvaro
> is complaining of might be better handled by ignoring temp tables
> while computing max freeze age etc.  I have some recollection that
> we'd intentionally included them, but I wonder why really; it's
> not like autovacuum is going to be able to do anything about an
> ancient temp table.

We can't truncate the clog, adapt the xid horizon, etc if there's any
temp tables. Otherwise you'd get failures when reading from one, no?

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Computing the conflict xid for index page-level-vacuum on primary
Next
From: Robert Haas
Date:
Subject: Re: New function pg_stat_statements_reset_query() to reset statisticsof a specific query