From: Mikko Partio <mpartio@gmail.com>
To: Fujii Masao <masao.fujii@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PANIC while doing failover (streaming replication)
Date: Fri, 1 Jul 2011 14:00:35 +0300
Message-ID: <BANLkTimmt2oFzWL6HfXPzxAkngfeWAwzAw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinjKdL1mDD7hLzCbqtSA_wCp6QP8A@mail.gmail.com>
References: <BANLkTi=3D0-3j6cD2-MJYDb0sxQmMb75aQ@mail.gmail.com>
<BANLkTinjKdL1mDD7hLzCbqtSA_wCp6QP8A@mail.gmail.com>
>
>
> 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
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: mpartio@gmail.com, masao.fujii@gmail.com, pgsql-hackers@postgresql.org
Subject: Re: PANIC while doing failover (streaming replication)
In-Reply-To: <BANLkTimmt2oFzWL6HfXPzxAkngfeWAwzAw@mail.gmail.com>
* 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