Date: Wed, 30 Nov 2011 13:34:20 -0800 (PST)
From: MirrorX <mirrorx@gmail.com>
To: pgsql-performance@postgresql.org
Message-ID: <1322688860656-5036800.post@n5.nabble.com>
In-Reply-To: <4ED69DCD.5000806@agliodbs.com>
References: <1322586733308-5033043.post@n5.nabble.com>
	<4ED69DCD.5000806@agliodbs.com>
Subject: Re: vacuum internals and performance affect
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

thx a lot for your answer :)

so when a transaction is still open from a while back (according to the
transactionID), no 'new dead' tuples can be marked as re-usable space for
new rows, right? by 'new dead' i mean that for example there is a
transaction running from 10.00am(with a specific transactionID). when i
delete rows at 11.00am these are the ones i am referring to.

the same thing happens with the index, right? the dead enties for the rows
that were deleted at 11.00am cannot be removed yet (this is not based on the
timestamp, i get it, i just want to point out that due to MVCC these rows
should be visible to the old transaction and by using timestamps this is
more obvious)

but, for these rows, the 'deleted' ones. does vacuum do anything at all at
that time? and if so, what is it? thx in advance

--
View this message in context: http://postgresql.1045698.n5.nabble.com/vacuum-internals-and-performance-affect-tp5033043p5036800.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.