X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B493ED89E6 for ; Thu, 8 Sep 2005 13:29:08 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 44405-04 for ; Thu, 8 Sep 2005 16:29:06 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id A548ED89C3 for ; Thu, 8 Sep 2005 13:29:02 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j88GStor007576; Thu, 8 Sep 2005 12:28:55 -0400 (EDT) To: Alvaro Herrera Cc: Adam Witney , pgsql-admin , Michael Fuhr Subject: Re: pg_dump error... Follow up In-reply-to: <20050908155621.GB13949@surnet.cl> References: <6689.1126190796@sss.pgh.pa.us> <20050908155621.GB13949@surnet.cl> Comments: In-reply-to Alvaro Herrera message dated "Thu, 08 Sep 2005 11:56:21 -0400" Date: Thu, 08 Sep 2005 12:28:55 -0400 Message-ID: <7575.1126196935@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 required=5 tests=[AWL=0.006] X-Spam-Level: X-Archive-Number: 200509/84 X-Sequence-Number: 18821 Alvaro Herrera writes: > To Tom: could this be caused by a WAL recovery that wrote a page image > to the wrong table? I guess it is very unlikely because the CRC of the > WAL record would likely not match, but it's an idea. I don't see any reason to think that WAL recovery would be more likely to cause this than normal operation. If it is a Postgres bug, my thoughts were pointing in the direction of a race condition that somehow allows the tag (identifier) of a buffer to be changed before it gets written out. I don't see any way that could happen ... but given the very small number of reports of such problems (i.e. 1) it would definitely have to be induced by some really low-probability event, such as a race condition with a very narrow window. Or it might not be our bug. We've certainly seen previous cases in which either the kernel or the disk drive wrote the wrong data --- it could be that this is the same thing, only it happened that the "wrong data" was some other Postgres data that happened to be passing through the system at about the same time. regards, tom lane