From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Ruslan A. Bondar <fsat@list.ru>
Cc: pgsql-admin@postgresql.org
Subject: Re: How to deal with corrupted database?
Date: Wed, 09 Nov 2011 09:57:37 -0600
Message-ID: <4EBA4E910200002500042BEC@gw.wicourts.gov> (raw)
In-Reply-To: <20111109195350.51c1b014@list.ru>
References: <20111109150225.076c2f38@list.ru>
<4EBA460E0200002500042BCD@gw.wicourts.gov>
<20111109195350.51c1b014@list.ru>
"Ruslan A. Bondar" <fsat@list.ru> wrote:
> No, this was a clean install of 9.0.x.
Then it isn't related to the issue I raised.
> Maybe It was upgraded from 9.0.3 to 9.0.4. I'm not sure.
You don't normally use pg_upgrade for that; this was a pg_upgrade bug.
-Kevin
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: Kevin.Grittner@wicourts.gov, fsat@list.ru
Subject: Re: How to deal with corrupted database?
In-Reply-To: <4EBA4E910200002500042BEC@gw.wicourts.gov>
* 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