Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id BB7A21337B81 for ; Wed, 2 Mar 2011 17:45:27 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 64952-06; Wed, 2 Mar 2011 21:45:21 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from spinlock.commandprompt.com (host-215.commandprompt.net [207.173.203.215]) by mail.postgresql.org (Postfix) with ESMTP id AECE31337B68; Wed, 2 Mar 2011 17:45:19 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by spinlock.commandprompt.com (Postfix) with ESMTP id 22CAB34804C; Wed, 2 Mar 2011 13:45:19 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at commandprompt.com Received: from spinlock.commandprompt.com ([127.0.0.1]) by localhost (spinlock.commandprompt.com.commandprompt.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jfeF+n6HzzqQ; Wed, 2 Mar 2011 13:45:17 -0800 (PST) Received: from perhan.alvh.no-ip.org (unknown [190.95.20.220]) by spinlock.commandprompt.com (Postfix) with ESMTPSA id C2D83348046; Wed, 2 Mar 2011 13:45:16 -0800 (PST) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id C7B096E3F7; Wed, 2 Mar 2011 18:45:13 -0300 (CLST) Content-Type: text/plain; charset=UTF-8 Cc: Heikki Linnakangas , Maxim Boguk , Fujii Masao , pgsql-admin , PostgreSQL-development Subject: Re: [HACKERS] Re: PD_ALL_VISIBLE flag was incorrectly set happend during repeatable vacuum From: Alvaro Herrera To: daveg In-reply-to: <20110302213034.GO26397@sonic.net> References: <4D2D6A56.9060808@enterprisedb.com> <20110228212832.GH26397@sonic.net> <4D6C1B16.6030708@enterprisedb.com> <20110301212043.GN26397@sonic.net> <20110302213034.GO26397@sonic.net> Date: Wed, 02 Mar 2011 18:45:13 -0300 Message-Id: <1299101996-sup-4206@alvh.no-ip.org> User-Agent: Sup/git Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201103/18 X-Sequence-Number: 36890 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 The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support