Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id D1AA7B5DBDE for ; Fri, 1 Jul 2011 08:00:43 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 68914-01; Fri, 1 Jul 2011 11:00:37 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.216.181]) by mail.postgresql.org (Postfix) with ESMTP id D8F1EB5DBDA; Fri, 1 Jul 2011 08:00:35 -0300 (ADT) Received: by qyk9 with SMTP id 9so1811605qyk.19 for ; Fri, 01 Jul 2011 04:00:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Xm+GP/xzv7DJxSxw5yUMugapAWxh4zCn5dOtYLKieHI=; b=v4dQaW0F/aQhRh3zB8ce5VhknKBlUU6lCzsMYGo10QKqUL14gKYfDzUukNg9qN+Bt/ FvtUr20x2DRLHVXWYSnXxLcQZJTtmu8vzZF6DLw+Xs9eHPbJ6LlbbNBqVz3OboiwMVZF xdn31Gn++gmJBV/VLVVrvFRubQGzSuQQtUkYw= MIME-Version: 1.0 Received: by 10.224.28.77 with SMTP id l13mr2332623qac.366.1309518035715; Fri, 01 Jul 2011 04:00:35 -0700 (PDT) Received: by 10.224.28.201 with HTTP; Fri, 1 Jul 2011 04:00:35 -0700 (PDT) In-Reply-To: References: Date: Fri, 1 Jul 2011 14:00:35 +0300 Message-ID: Subject: Re: PANIC while doing failover (streaming replication) From: Mikko Partio To: Fujii Masao Cc: pgsql-admin , PostgreSQL-development Content-Type: multipart/alternative; boundary=0015175caa2458888d04a6ffedd7 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=2.421 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, FS_REPLICA=3.599, HTML_MESSAGE=0.001, SARE_SPEC_REPLICA=0.72 X-Spam-Level: ** X-Archive-Number: 201107/6 X-Sequence-Number: 37785 --0015175caa2458888d04a6ffedd7 Content-Type: text/plain; charset=ISO-8859-1 > > > http://archives.postgresql.org/pgsql-hackers/2008-12/msg01335.php > According to the above thread, this issue seems to exist for a few years, > and be unsolved yet. Could you provide a self-contained test case? I can try ... In related to this, after the failover we got several other worrying messages in the log. During vacuums lots of these: WARNING: relation "pg_largeobject" page 5333088 is uninitialized --- fixing For several different tables. I gather that since these are mere WARNINGs they do not affect the server functionality or data integrity? Then, for one table we got: ERROR: unexpected chunk number 2 (expected 0) for toast value 4398162 in pg_toast_1247555 which is quite worrying since we had to restore that table from backups. Are these errors caused by the PANIC'd shutdown or are they a symptom of something else. The servers are quite new and no server crashes have happened. Regards Mikko --0015175caa2458888d04a6ffedd7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

http://archives.postgresql.org/pgsql-hacke= rs/2008-12/msg01335.php
According to the above thread, this issue seems to exist for a few years, and be unsolved yet. Could you provide a self-contained test case?

I can try ...=A0

In relate= d to this, after the failover we got several other worrying messages in the= log.

During vacuums lots of these:

= WARNING: =A0relation "pg_largeobject" page 5333088 is uninitializ= ed --- fixing

For several different tables. I gath= er that since these are mere WARNINGs they do not affect the server functio= nality or data integrity? Then, for one table we got:

ERROR: =A0unexpected chunk number 2 (expected 0) for to= ast value 4398162 in pg_toast_1247555

which is qui= te worrying since we had to restore that table from backups. Are these erro= rs caused by the PANIC'd shutdown or are they a symptom of something el= se. The servers are quite new and no server crashes have happened.=A0

Regards

Mikko
--0015175caa2458888d04a6ffedd7--