Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

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: Fri, 27 Oct 2006 11:52:36 -0400
  • Message-id: <6330(dot)1161964356(at)sss(dot)pgh(dot)pa(dot)us>

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



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group