Re: BUG #2594: Gin Indexes cause server to crash on Windows - Mailing list pgsql-bugs

From Bernhard Weisshuhn
Subject Re: BUG #2594: Gin Indexes cause server to crash on Windows
Date
Msg-id 20060830095905.GA20345@weisshuhn.de
Whole thread Raw
In response to Re: BUG #2594: Gin Indexes cause server to crash on Windows  (Charlie Savage <cfis@savagexi.com>)
Responses Re: BUG #2594: Gin Indexes cause server to crash on Windows  (Teodor Sigaev <teodor@sigaev.ru>)
Re: BUG #2594: Gin Indexes cause server to crash on Windows  (Charlie Savage <cfis@savagexi.com>)
List pgsql-bugs
On Tue, Aug 29, 2006 at 05:13:40PM -0600, Charlie Savage <cfis@savagexi.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

pgsql-bugs by date:

Previous
From: "Filip Hrbek"
Date:
Subject: Re: Partially corrupted table
Next
From: "Filip Hrbek"
Date:
Subject: Re: Partially corrupted table