From: | Charlie Savage <cfis(at)savagexi(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #2594: Gin Indexes cause server to crash on Windows |
Date: | 2006-08-30 16:59:24 |
Message-ID: | 44F5C3EC.7010208@savagexi.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Backport also works fine on Windows and Linux x86_32 (Fedora Core 5).
Charlie
Bernhard Weisshuhn wrote:
> On Tue, Aug 29, 2006 at 05:13:40PM -0600, Charlie Savage <cfis(at)savagexi(dot)com> wrote:
>
>>> Tom Lane wrote:
>>>
>>>> It appears that building a gin index on an empty table fails on any
>>>> platform. I get a null pointer dereference with the following stack
>>>> trace
>
>> Teodor Sigaev wrote:
>>
>>> Fixed in HEAD, thank you
>
> For the sake of completeness/reference: The backport for 8.1
> (http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/gin_tsearch2_81.gz)
> doesn't seem to have this bug, at least on a linux x86_64 machine I can
> create empty gin indexes with no problem.
>
> And the performance is sweeeet! Thanks Oleg & Teodor!
>
> kind regards,
> bkw
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Tolley | 2006-08-30 17:29:56 | BUG #2599: AM/PM doesn't work in to_timestamp in the middle of a string |
Previous Message | Tom Lane | 2006-08-30 16:37:56 | Re: BUG #2598: Columns named R are not accessible - although R is not a keyword |