Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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 10:46:40 -0400
Richard Broersma Jr <rabroersma(at)yahoo(dot)com> writes: >> So what do you get from 'select * from pg_index where indrelid = 16737' ? >> If that crashes, which individual columns can you select from the row? > I found the exact row and column that causes the server to crash. > http://archives.postgresql.org/pgsql-general/2006-10/msg01320.php That didn't answer my question. regards, tom lane
- Follow-Ups:
- Re: pg_dumpall failing from possible corrupted shared memory
- From: Richard Broersma Jr
- Re: pg_dumpall failing from possible corrupted shared memory
- References:
- Re: pg_dumpall failing from possible corrupted shared memory
- From: Richard Broersma Jr
- Re: pg_dumpall failing from possible corrupted shared memory
- Prev by Date: Re: plpython
- Next by Date: Re: skip duplicate key error during inserts
- Previous by thread: Re: pg_dumpall failing from possible corrupted shared memory
- Next by thread: Re: pg_dumpall failing from possible corrupted shared memory
- Indexes: