| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: removal of dangling temp tables |
| Date: | 2018-12-14 18:40:08 |
| Message-ID: | 20181214184008.texevy73ajq6air6@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-12-14 18:44:04 | Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query |
| Previous Message | Alexander Korotkov | 2018-12-14 18:39:48 | Re: Computing the conflict xid for index page-level-vacuum on primary |