From: MirrorX <mirrorx@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: vacuum internals and performance affect
Date: Wed, 30 Nov 2011 13:34:20 -0800 (PST)
Message-ID: <1322688860656-5036800.post@n5.nabble.com> (raw)
In-Reply-To: <4ED69DCD.5000806@agliodbs.com>
References: <1322586733308-5033043.post@n5.nabble.com>
<4ED69DCD.5000806@agliodbs.com>
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.ht...
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
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: mirrorx@gmail.com
Subject: Re: vacuum internals and performance affect
In-Reply-To: <1322688860656-5036800.post@n5.nabble.com>
* 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