From: | "David Parker" <dparker(at)tazznetworks(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "postgres general" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: index xyz is not a btree |
Date: | 2005-06-10 20:08:25 |
Message-ID: | 07FDEE0ED7455A48AC42AC2070EDFF7C746FEE@corpsrv2.tazznetworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
No, I haven't tried that - I wasn't aware of pg_filedump. What's tricky
is that when the build detects a failure, it deletes the output
directory (so we don't get left with a half-built db) so I'll have to
fiddle with it....
I just downloaded pg_filedump from the redhat site, so I'll play around
with it, and report back if/when I find anything.
Thanks.
- DAP
>> 1) always the same index - "attribute_pkey" on our "attirbute"
>> table
>> - one created implicitly by a primary key constraint
>> 2) the error happens during a vacuum command
>
>Hmm ... that seems a bit too consistent for a hardware issue
>doesn't it?
>
>Have you looked at the index file with pg_filedump, or even just od?
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Marc Munro | 2005-06-10 21:33:33 | Waiting for select |
Previous Message | H Hale | 2005-06-10 19:59:26 | Re: foreign key constraint not being respected with type created by CREATE TYPE |