Re: pg_dumpall failing from possible corrupted shared memory

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Richard Broersma Jr <rabroersma(at)yahoo(dot)com>
Cc: General PostgreSQL List <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_dumpall failing from possible corrupted shared memory
Date: 2006-10-27 15:52:36
Message-ID: 6330.1161964356@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Richard Broersma Jr <rabroersma(at)yahoo(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Clodoaldo Pinto Neto 2006-10-27 16:06:58 Re: plpython.so
Previous Message Tom Lane 2006-10-27 15:46:10 Re: plpython.so