Re: Postgres dies when using an intarray operator

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: jeroen van iddekinge <iddekingej(at)lycos(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Postgres dies when using an intarray operator
Date: 2006-04-01 16:44:30
Message-ID: 20060401164430.GA55895@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Apr 01, 2006 at 03:40:19PM +0200, jeroen van iddekinge wrote:
> When using intarray operator in a query, postgres dies and restart
> itself when executing the following query:
>
> select r1.bet_sentence & r2.bet_sentence
> from related r1,related r2
> where r1.bet_sentence && r2.bet_sentence

Here's a complete test case:

CREATE TABLE foo (a integer[]);

INSERT INTO foo (a)
SELECT array[random() * 10, random() * 10, random() * 10]
FROM generate_series(1, 24);

CREATE INDEX foo_a_idx ON foo USING gist (a gist__int_ops);

SET enable_seqscan TO off;
SELECT f1.a & f2.a FROM foo f1, foo f2 WHERE f1.a && f2.a;

This crashes for me in 8.1.3 on FreeBSD 6.1-PRERELEASE and Solaris 9.
An assert-enabled 8.1.3 logs the following:

TRAP: BadArgument("!(((header->context) != ((void *)0) && (((((Node*)((header->context)))->type) == T_AllocSetContext))))", File: "mcxt.c", Line: 612)

--
Michael Fuhr

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Agent M 2006-04-01 17:26:08 Re: control pg_hba.conf via SQL
Previous Message Andrew Dunstan 2006-04-01 15:47:39 Re: Suggestion: Which Binary?