Re: Temporary tables versus wraparound... again

From: Andres Freund <andres(at)anarazel(dot)de>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Noah Misch <noah(at)leadboat(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Temporary tables versus wraparound... again
Date: 2022-12-06 18:59:05
Message-ID: 20221206185905.kxvrnvso34pyw7yf@awork3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2022-12-06 13:47:39 -0500, Greg Stark wrote:
> So.... I talked about this patch with Ronan Dunklau and he had a good
> question.... Why are we maintaining relfrozenxid and relminmxid in
> pg_class for temporary tables at all? Autovacuum can't use them and
> other sessions won't care about them. The only session that might care
> about them is the one attached to the temp schema.

Uh, without relfrozenxid for temp tables we can end up truncating clog
"ranges" away that are required to access the temp tables. So this would
basically mean that temp tables can't be used reliably anymore.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2022-12-06 19:00:33 Re: generic plans and "initial" pruning
Previous Message Andres Freund 2022-12-06 18:53:53 Re: 16: Collation versioning and dependency helpers