pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Pavan Deolasee <pavan.deolasee@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Gregory Stark <stark@enterprisedb.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Hmmm ... isn't count_nondeletable_pages all wet?
Date: Sun, 16 Sep 2007 22:06:45 +0530
Message-ID: <2e78013d0709160936t1eec56e4ycbb17da6be9a9df4@mail.gmail.com> (raw)
In-Reply-To: <5354.1189955695@sss.pgh.pa.us>
References: <28916.1189900143@sss.pgh.pa.us>
	<29644.1189904237@sss.pgh.pa.us>
	<87fy1fkk6p.fsf@oxford.xeocode.com>
	<5354.1189955695@sss.pgh.pa.us>

On 9/16/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
>
> Couldn't say.  Those two were on my mind because the reporters had
> allowed me to troll through their table and index files and verify
> that there were indeed multiple index pointers to the same table row,
> and yet the index itself did not show any indication of corruption.
> I had noticed the "clumping" pattern of the doubly-linked rows in
> both cases, but hadn't found an explanation.
>
>
This was a nice catch indeed! I remember we fixed a similar issue
with VACUUM FULL few months back. Such issues would become
prominent with HOT because of early vacuuming and reuse of
tuples. Also unlike current VACUUM which runs exclusively on a table
(i.e. no two vacuums are allowed to run on a table simultaneously),
HOT makes concurrent pruning and vacuuming of a table possible.

In fact, during HOT development and testing cycles, I faced
similar race conditions a few times. This is just to keep ourselves aware of
the changes introduced by HOT. Hopefully by now we have fixed most of
the outstanding bugs in the HOT code (and Tom's eyes would catch the
remaining, if any :-)). Fingers crossed.

Thanks,
Pavan


-- 
Pavan Deolasee
EnterpriseDB     http://www.enterprisedb.com

view thread (6+ messages)  latest in thread

Message-ID: <2e78013d0709160936t1eec56e4ycbb17da6be9a9df4@mail.gmail.com>
Permalink:  ../2e78013d0709160936t1eec56e4ycbb17da6be9a9df4@mail.gmail.com/
Also on:    postgresql.org/message-id/2e78013d0709160936t1eec56e4ycbb17da6be9a9df4@mail.gmail.com

 · 

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-admin@postgresql.org
  Cc: pavan.deolasee@gmail.com, tgl@sss.pgh.pa.us, stark@enterprisedb.com, pgsql-hackers@postgresql.org
  Subject: Re: Hmmm ... isn't count_nondeletable_pages all wet?
  In-Reply-To: <2e78013d0709160936t1eec56e4ycbb17da6be9a9df4@mail.gmail.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