From: Stephen Frost <sfrost@snowman.net>
To: Terry Schmitt <tschmitt@schmittworks.com>
Cc: Craig Ringer <ringerc@ringerc.id.au>
Cc: pgsql-admin@postgresql.org
Subject: Re: Data corruption after SAN snapshot
Date: Tue, 7 Aug 2012 21:39:31 -0400
Message-ID: <20120808013931.GO1267@tamriel.snowman.net> (raw)
In-Reply-To: <CAOOcysxktC6qkc0j4cruhtA5Ec5BLDb9Q0hX9YWkb8G7F1_JdA@mail.gmail.com>
References: <CAOOcyswLYBfJDuvNBPMkiNCGNKgK=SiexUuTVHCh2O+Y1T-sLw@mail.gmail.com>
<5021BCA6.7030000@ringerc.id.au>
<CAOOcysxktC6qkc0j4cruhtA5Ec5BLDb9Q0hX9YWkb8G7F1_JdA@mail.gmail.com>
Terry,
* Terry Schmitt (tschmitt@schmittworks.com) wrote:
> So far, executing pg_dumpall
> seems to be fairly reliable for finding the corrupt objects after my
> initial data load, but unfortunately much of the corruption has been with
> indexes which pgdump will not expose.
Shouldn't be too hard to write a script that'll do a query against each
table using an ORDER BY that matches each index, at least for 'simple'
indexes, which'll typically cause an in-order index traversal.
Just a thought.
Thanks,
Stephen
Attachments:
signature.asc (application/pgp-signature, 197B) download
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: sfrost@snowman.net, tschmitt@schmittworks.com, ringerc@ringerc.id.au
Subject: Re: Data corruption after SAN snapshot
In-Reply-To: <20120808013931.GO1267@tamriel.snowman.net>
* 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