Re: [HACKERS] Fix for initdb/indexing problems

From: Keith Parks <emkxp01(at)mtcc(dot)demon(dot)co(dot)uk>
To: hackers(at)postgresql(dot)org, maillist(at)candle(dot)pha(dot)pa(dot)us
Subject: Re: [HACKERS] Fix for initdb/indexing problems
Date: 1998-09-03 09:25:37
Message-ID: 199809030925.KAA18833@mtcc.demon.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce,

Just to confirm, your fixes are just the job.

The regression tests run fine with only the failures I have always
seen due to maths precision and SIGFPE handling.

Thanks for your persistence in tracking this "bug" down.

Keith.

Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
>
> OK, I have found the problem. I looked AGAIN at CatalogIndexInsert(),
> because all problems seem to be localized there. I remembered something
> Tom Szybist said yesterday while we were on the phone about Datum only
> being one value.
>
> I said they are chained together, which I saw in IndexFormDatum, but
> when I looked, I saw that the Datum pointer indexed in IndexFormDatum
> was only a single Datum value, not an array of datum values like nulls
> is defined.
>
> With single-key system indexes, this was not a problem, but with the new
> multi-key system indicies, it is.
>
> I have attached the patch, and it is applied to the tree. Please let me
> know if this fixes the many reported index problems. It should.
>

Browse pgsql-hackers by date

  From Date Subject
Next Message mummert&partner_meskesm 1998-09-03 11:42:19 Index problems
Previous Message Tatsuo Ishii 1998-09-03 09:17:50 Re: [HACKERS] USE_LOCALE and unsigned char *