Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Re: PD_ALL_VISIBLE flag was incorrectly set happend during repeatable vacuum

From: Greg Stark <gsstark(at)mit(dot)edu>
To: David Christensen <david(at)endpoint(dot)com>
Cc: daveg <daveg(at)sonic(dot)net>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] Re: PD_ALL_VISIBLE flag was incorrectly set happend during repeatable vacuum
Date: 2011-03-01 03:32:23
Message-ID: AANLkTi=xq4SV6jwA7txvrbEWocyeiU6XiTG=-zVy+7Dq@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-hackers
On Tue, Mar 1, 2011 at 1:43 AM, David Christensen <david(at)endpoint(dot)com> wrote:
> Was this cluster upgraded to 8.4.4 from 8.4.0?  It sounds to me like a known bug in 8.4.0 which was fixed by this commit:
>

The reproduction script described was running vacuum repeatedly. A
single vacuum run out to be sufficient to clean up the problem if it
was left-over.

I wonder if it would help to write a regression test that runs 100 or
so vacuums and see if the bulid farm turns up any examples of this
behaviour.

-- 
greg

In response to

Responses

pgsql-hackers by date

Next:From: Joachim WielandDate: 2011-03-01 04:27:44
Subject: Re: Snapshot synchronization, again...
Previous:From: Fujii MasaoDate: 2011-03-01 03:05:08
Subject: Re: [HACKERS] Re: PD_ALL_VISIBLE flag was incorrectly set happend during repeatable vacuum

pgsql-admin by date

Next:From: GnanakumarDate: 2011-03-01 07:53:12
Subject: How to upgrade PostgreSQL minor releases without a dump/restore?
Previous:From: Fujii MasaoDate: 2011-03-01 03:05:08
Subject: Re: [HACKERS] Re: PD_ALL_VISIBLE flag was incorrectly set happend during repeatable vacuum

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group