Tom,
Sorry about that. It's 7.2.1 on RedHat 7.2.
I wasn't able to delete; whenever the database touched those records (even
to do a delete) the backend would crash.
It turns out that my problems were much deeper than I thought. There was a
bad dimm in the machine wreaking havoc.
Thanks for the pointer to pg_filedump.
Thanks,
Peter Darley
-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org]On Behalf Of Tom Lane
Sent: Tuesday, July 02, 2002 12:00 PM
To: Peter Darley
Cc: Pgsql-General
Subject: Re: [GENERAL] Bad records in table
"Peter Darley" <pdarley@kinesis-cem.com> writes:
> I can identify the bad records with a simple perl script that reads all
the
> records sequentially and lets me know which ones crash the back end. Now
> that I know which ones they are, how can I get rid of them?
DELETE?
That might not work very well if the corruption is in toasted fields,
but you haven't given any details that would let us know (not even such
basic info as your PG version).
But before doing that I'd suggest eyeballing the bad data using a tool
such as pg_filedump (see http://sources.redhat.com/rhdb/tools.html).
Look at the "ctid" column of the bad tuples to see what part of the
file you need to dump (ctid is block number and item number). The
pattern of the corruption might give some clue what happened.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly
