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

From Richard Broersma Jr
Subject Re: pg_dumpall failing from possible corrupted shared memory
Date
Msg-id 20061027210543.77996.qmail@web31802.mail.mud.yahoo.com
Whole thread Raw
In response to Re: pg_dumpall failing from possible corrupted shared memory  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_dumpall failing from possible corrupted shared memory
List pgsql-general
> >> 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.

mydb=# select ctid from pg_index where indrelid = 16737 and indexrelid = 604251;
  ctid
--------
 (1,11)
(1 row)
mydb=# select relfilenode from pg_class where relname = 'pg_index';
 relfilenode
-------------
        2610
(1 row)
mydb=# select oid from pg_database where datname = 'mydb';
  oid
-------
 16393
(1 row)

postgres@db_server01 ~ $ ./pg_filedump -i -f -R 1 /var/lib/pgsql/data/base/16393/2610 >
./results.log

I've attached the results.log to the email.

Regards,

Richard Broersma Jr.

Attachment

pgsql-general by date:

Previous
From: "Clodoaldo Pinto Neto"
Date:
Subject: Re: plpython
Next
From: Tom Lane
Date:
Subject: Re: Simple OUTER JOIN doubt