Re: BitmapHeapScan streaming read user and prelim refactoring - Mailing list pgsql-hackers

From Tom Lane
Subject Re: BitmapHeapScan streaming read user and prelim refactoring
Date
Msg-id 4027183.1714089439@sss.pgh.pa.us
Whole thread Raw
In response to Re: BitmapHeapScan streaming read user and prelim refactoring  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BitmapHeapScan streaming read user and prelim refactoring
List pgsql-hackers
I wrote:
> Hmm, is that actually true?  There's no more reason to think a tuple
> in a temp table is old enough to be visible to all other sessions
> than one in any other table.  It could be all right if we had a
> special-case rule for setting all-visible in temp tables.  Which
> indeed I thought we had, but I can't find any evidence of that in
> vacuumlazy.c, nor did a trawl of the commit log turn up anything
> promising.  Am I just looking in the wrong place?

Ah, never mind that --- I must be looking in the wrong place.
Direct experimentation proves that VACUUM will set all-visible bits
for temp tables even in the presence of concurrent transactions.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Chris Cleveland
Date:
Subject: Index access method not receiving an orderbys ScanKey
Next
From: Robert Haas
Date:
Subject: Re: New GUC autovacuum_max_threshold ?