public inbox for [email protected]  

help / color / mirror / Atom feed
From: Tom Lane <[email protected]>
To: Melanie Plageman <[email protected]>
Cc: Tomas Vondra <[email protected]>
Cc: Michael Paquier <[email protected]>
Cc: Thomas Munro <[email protected]>
Cc: Heikki Linnakangas <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: Pg Hackers <[email protected]>
Cc: Nazir Bilal Yavuz <[email protected]>
Subject: Re: BitmapHeapScan streaming read user and prelim refactoring
Date: Thu, 25 Apr 2024 19:57:19 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <20240406134011.hjo3e2336sgcghfp@liskov>
	<[email protected]>
	<20240406160423.r2zcjex3dngnztx4@liskov>
	<20240406213450.fatgalewqkbez4tg@liskov>
	<[email protected]>
	<20240407041734.74jwo5wjmxs6p5du@liskov>
	<[email protected]>
	<CAAKRu_Zg8Bj66OZD46Jd-ksh02OGrPR8z0JLPQqEZNEHASi6uw@mail.gmail.com>
	<[email protected]>
	<CAAKRu_bTXNe16j=mFASOBrkzD=uvfUUqqOwE1FDsT7YvA1P=Pg@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<CAAKRu_YA2YBQNr+qE_hq-a4ohqDx+dD2wWekzOhmMUmYcJ0Knw@mail.gmail.com>
	<CAAKRu_YVQdGVYFAu7ng84GvHWXoSvpBtz+xktm1nUB7H48Pj-Q@mail.gmail.com>
	<[email protected]>
	<CAAKRu_ZkL=BUB4FWx+P3Wcf-JiDYSf-NkuPm3Z94G3So+S=R0w@mail.gmail.com>
	<CAAKRu_atCg2KXyTOzbDqq8FZNPDZj7sn6YvkeL=dzn=9d4Eaug@mail.gmail.com>
	<[email protected]! s>

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






view thread (27+ messages)  latest in thread

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: BitmapHeapScan streaming read user and prelim refactoring
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox