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 <[EMAIL PROTECTED]>
wrote:
Tom Lane wrote:
It appears that building a gin index on an empty table fails on any
platform. I get a
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.
It hasn't, because 8.2 already goes forward:
Fixed in HEAD, thank you
Tom Lane wrote:
"Gin Indexes cause server to crash on Windows" <[EMAIL PROTECTED]> writes:
CREATE TABLE test (
vector tsvector NOT NULL
);
CREATE INDEX idx_test_vector ON test USING gin (vector);
server closed the connection unexpectedly
It appears that building a g
On Tue, Aug 29, 2006 at 05:13:40PM -0600, Charlie Savage <[EMAIL PROTECTED]>
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 i
Works great now - thanks for the quick fix.
Charlie
Teodor Sigaev wrote:
Fixed in HEAD, thank you
Tom Lane wrote:
"Gin Indexes cause server to crash on Windows" <[EMAIL PROTECTED]>
writes:
CREATE TABLE test (
vector tsvector NOT NULL
);
CREATE INDEX idx_test_vector ON test USING gin (vecto
"Gin Indexes cause server to crash on Windows" <[EMAIL PROTECTED]> writes:
> CREATE TABLE test (
> vector tsvector NOT NULL
> );
> CREATE INDEX idx_test_vector ON test USING gin (vector);
> server closed the connection unexpectedly
It appears that building a gin index on an empty table fails on
The following bug has been logged online:
Bug reference: 2594
Logged by: Gin Indexes cause server to crash on Windows
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2 CVS-Aug 28
Operating system: Windows XP Pro
Description:Gin Indexes cause server to crash on
