When grilled further on (Mon, 30 Aug 2004 11:31:12 -0400), Tom Lane <[EMAIL PROTECTED]> confessed:
> Robert Creager <[EMAIL PROTECTED]> writes: > > While doing some daily processing, I ran across the following error: > > > ERROR: could not find a feasible split point for "obs_v_file_id_index" > > > file_id | integer | not null > > Inexes: "obs_v_file_id_index" btree (file_id) > > On an index on an *integer* column?? That's a can't-happen error in the > first place, and it's particularly silly when the index entries are > small and fixed-width. I surmise that you have a corrupted index, but > it would be interesting to examine the entrails. Is it repeatable? > Is the database small enough that you could ship me a tarball copy > (or if not, would you be willing to let me into your system to look at > it)? > > regards, tom lane The error is repeatable (with a script that runs in a few minutes). A recent dump 528Mb compressed (10Gb on disk). As for access, presumably you want in as postgres? Any chance you have a gpg key somewhere for encryption? I did a quick check and didn't find any... Cheers, Rob -- 20:00:25 up 16 days, 6:22, 3 users, load average: 3.79, 3.97, 3.99 Linux 2.6.5-02 #8 SMP Mon Jul 12 21:34:44 MDT 2004
pgp4PRbVvvd8F.pgp
Description: PGP signature
