From: Alvaro Herrera <alvherre@commandprompt.com>
To: daveg <daveg@sonic.net>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Maxim Boguk <maxim.boguk@gmail.com>
Cc: Fujii Masao <masao.fujii@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] Re: PD_ALL_VISIBLE flag was incorrectly set happend during repeatable vacuum
Date: Wed, 02 Mar 2011 18:45:13 -0300
Message-ID: <1299101996-sup-4206@alvh.no-ip.org> (raw)
In-Reply-To: <20110302213034.GO26397@sonic.net>
References: <AANLkTino+Gc2vvOVdzCPRRXW-N7R5=ikYMnNKT5W=mk1@mail.gmail.com>
<AANLkTikw==USr3+4Mt+w97P3ymux-Bhn0G7Ad0ZJHbqG@mail.gmail.com>
<4D2D6A56.9060808@enterprisedb.com>
<20110228212832.GH26397@sonic.net>
<4D6C1B16.6030708@enterprisedb.com>
<20110301212043.GN26397@sonic.net>
<20110302213034.GO26397@sonic.net>
Excerpts from daveg's message of mié mar 02 18:30:34 -0300 2011:
> After a restart and vacuum of all dbs with no other activity things were
> quiet for a couple hours and then we started seeing these PD_ALL_VISIBLE
> messages again.
>
> Going back through the logs we have been getting these since at least before
> mid January. Oddly, this only happens on four systems which are all new Dell
> 32 core Nehalem 512GB machines using iscsi partitions served off a Netapp.
> Our older 8 core 64GB hosts have never logged any of these errors. I'm not
> saying it is related to the hw, as these hosts are doing a lot more work than
> the old hosts so it may be a concurrency problem that just never came up at
> lower levels before.
>
> Postgresql version is 8.4.4.
I don't see how this could be related, but since you're running on NFS,
maybe it is, somehow:
http://archives.postgresql.org/message-id/4D40DDB7.1010000@credativ.com
(for example what if the visibility map fork's last page is overwritten?)
--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: alvherre@commandprompt.com, daveg@sonic.net, heikki.linnakangas@enterprisedb.com, maxim.boguk@gmail.com, masao.fujii@gmail.com, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Re: PD_ALL_VISIBLE flag was incorrectly set happend during repeatable vacuum
In-Reply-To: <1299101996-sup-4206@alvh.no-ip.org>
References: <AANLkTino+Gc2vvOVdzCPRRXW-N7R5=ikYMnNKT5W=mk1@mail.gmail.com> <AANLkTikw==USr3+4Mt+w97P3ymux-Bhn0G7Ad0ZJHbqG@mail.gmail.com> <4D2D6A56.9060808@enterprisedb.com> <20110228212832.GH26397@sonic.net> <4D6C1B16.6030708@enterprisedb.com> <20110301212043.GN26397@sonic.net> <20110302213034.GO26397@sonic.net> <1299101996-sup-4206@alvh.no-ip.org>
* 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