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 865044.52015.qm@web31814.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  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
> > mydb=# select pg_get_indexdef(indexrelid) from pg_index where indrelid = '16737';
> > server closed the connection unexpectedly
>
> 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

I believe that corrupted value should be:

CREATE INDEX index_daily ON process USING btree (date_trunc('day'::text, tstamp))

I tried to:

 select * from process;
 select * from process limit 1;
 explain analyze select * from process;

but they also crashes the server.

Regards,

Richard Broersma Jr.

pgsql-general by date:

Previous
From: km
Date:
Subject: plpython
Next
From: "Merlin Moncure"
Date:
Subject: Re: database not enforcing unqiue constriant