Re: PD_ALL_VISIBLE flag error on 9.0 alpha 4

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: PD_ALL_VISIBLE flag error on 9.0 alpha 4
Date: 2010-03-10 20:36:32
Message-ID: 1268253392.3825.2528.camel@ebony
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

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.

--
Simon Riggs www.2ndQuadrant.com

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2010-03-10 21:08:44 Re: PD_ALL_VISIBLE flag error on 9.0 alpha 4
Previous Message Chris Travers 2010-03-10 16:30:57 Re: Bug in triggers

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2010-03-10 21:08:44 Re: PD_ALL_VISIBLE flag error on 9.0 alpha 4
Previous Message Kevin Flanagan 2010-03-10 20:15:30 Re: Access violation from palloc, Visual Studio 2005, C-language function