Re: PD_ALL_VISIBLE flag error on 9.0 alpha 4

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: PD_ALL_VISIBLE flag error on 9.0 alpha 4
Date: 2010-03-10 21:08:44
Message-ID: 4B980A5C.3020901@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Simon Riggs wrote:
> On Tue, 2010-03-09 at 22:02 -0800, Josh Berkus wrote:
>
>> 1. Set up 9.0a4 doing SR replication with a 2nd 9.0a4
>> 2. Ran pgbench for a while.
>> 3. Aborted pgbench with Ctl-C
>> 4. Changed vacuum_defer_cleanup_age in postgresql.conf and reloaded
>> 5. Ran pgbench again, and got:
>>
>> Sidney-Stratton:pg90 josh$ pgbench -c 2 -T 300 bench
>> starting vacuum...WARNING: PD_ALL_VISIBLE flag was incorrectly set in
>> relation "pgbench_branches" page 0
>> WARNING: PD_ALL_VISIBLE flag was incorrectly set in relation
>> "pgbench_branches" page 1
>> WARNING: PD_ALL_VISIBLE flag was incorrectly set in relation
>> "pgbench_tellers" page 0
>> WARNING: PD_ALL_VISIBLE flag was incorrectly set in relation
>> "pgbench_tellers" page 1
>
> Understandable.
>
> Time to remove vacuum_defer_cleanup_age, I think.

Umm, so what's the bug?

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Simon Riggs 2010-03-10 22:45:25 Re: PD_ALL_VISIBLE flag error on 9.0 alpha 4
Previous Message Simon Riggs 2010-03-10 20:36:32 Re: PD_ALL_VISIBLE flag error on 9.0 alpha 4

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-03-10 22:42:51 Re: Access violation from palloc, Visual Studio 2005, C-language function
Previous Message Simon Riggs 2010-03-10 20:36:32 Re: PD_ALL_VISIBLE flag error on 9.0 alpha 4