pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Manfred Koizar <mkoi-pg@aon.at>
Cc: Jochem van Dieten <jochemd@oli.tudelft.nl>
Cc: pgsql-performance@postgresql.org
Subject: Re: planner/optimizer question
Date: Fri, 30 Apr 2004 21:19:39 -0400
Message-ID: <8881.1083374379@sss.pgh.pa.us> (raw)
In-Reply-To: <toe590tgu39ilahg3p1os2mjlgf4iss582@email.aon.at>
References: <pvc290584alms4s6hurvsh5ra09ki7se1s@email.aon.at>
	<409290F0.10509@oli.tudelft.nl>
	<toe590tgu39ilahg3p1os2mjlgf4iss582@email.aon.at>

Manfred Koizar <mkoi-pg@aon.at> writes:
> Yes, the visible-to-all flag would be set as a by-product of an index
> scan, if the heap tuple is found to be visible to all active
> transactions.  This update is non-critical

Oh really?  I think you need to think harder about the transition
conditions.

Dead-to-all is reasonably safe to treat as a hint bit because *it does
not ever need to be undone*.  Visible-to-all does not have that
property.

			regards, tom lane



view thread (37+ messages)  latest in thread

Message-ID: <8881.1083374379@sss.pgh.pa.us>
Permalink:  ../8881.1083374379@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/8881.1083374379@sss.pgh.pa.us

 · 

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: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, mkoi-pg@aon.at, jochemd@oli.tudelft.nl
  Subject: Re: planner/optimizer question
  In-Reply-To: <8881.1083374379@sss.pgh.pa.us>

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

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