Re: Temp table handling after anti-wraparound shutdown (Was: BUG#15840) - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Temp table handling after anti-wraparound shutdown (Was: BUG#15840)
Date
Msg-id 20190608014540.GC7228@paquier.xyz
Whole thread Raw
In response to Re: Temp table handling after anti-wraparound shutdown (Was: BUG#15840)  (Andres Freund <andres@anarazel.de>)
Responses Re: Temp table handling after anti-wraparound shutdown (Was: BUG#15840)
List pgsql-hackers
On Fri, Jun 07, 2019 at 05:26:32PM -0700, Andres Freund wrote:
> I was more thinking that we'd move the check for orphaned-ness into a
> separate function (maybe IsOrphanedRelation()), and move the code to
> drop orphan relations into a separate function (maybe
> DropOrphanRelations()). That'd limit the amount of code duplication for
> doing this both in autovacuum and all-database vacuums quite
> considerably.

A separation makes sense.  At some point we should actually try to
separate vacuum and orphan relation cleanup, so separate functions
make sense.  The only reason why we are doing it with autovacuum is
that it is the only thing in-core spawning a worker connected to a
database which does a full scan of pg_class.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: be-gssapi-common.h should be located in src/include/libpq/
Next
From: Avinash Kumar
Date:
Subject: Bloom Indexes - bit array length and the total number of bits (orhash functions ?? ) !