Re: pg_dumpall failing from possible corrupted shared memory - Mailing list pgsql-general

From Tom Lane
Subject Re: pg_dumpall failing from possible corrupted shared memory
Date
Msg-id 6330.1161964356@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dumpall failing from possible corrupted shared memory  (Richard Broersma Jr <rabroersma@yahoo.com>)
Responses Re: pg_dumpall failing from possible corrupted shared memory  (Richard Broersma Jr <rabroersma@yahoo.com>)
List pgsql-general
Richard Broersma Jr <rabroersma@yahoo.com> writes:
>> Are you interested in dumping out the page of pg_index that
>> contains this record, using pg_filedump?

> Sure, only how do I use pg_filedump?

Find out the ctid of the busted pg_index record; the first part of it is
the page number.  Then

    pg_filedump -i -f -R page_number pg_index_filename >resultfile

The filename is whatever "select relfilenode from pg_class where relname
= 'pg_index'" tells you, in whatever subdirectory of $PGDATA/base
"select oid from pg_database where datname = 'yourdb'" tells you.

Oh, if you don't have pg_filedump, get it from
http://sources.redhat.com/rhdb/
Be sure to get the one matching your PG version.

            regards, tom lane

pgsql-general by date:

Previous
From: Richard Broersma Jr
Date:
Subject: Re: pg_dumpall failing from possible corrupted shared memory
Next
From: "Clodoaldo Pinto Neto"
Date:
Subject: Re: plpython.so