Re: Postgres dies when using an intarray operator

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: jeroen van iddekinge <iddekingej(at)lycos(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Postgres dies when using an intarray operator
Date: 2006-04-02 01:20:17
Message-ID: 16936.1143940817@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Fuhr <mike(at)fuhr(dot)org> writes:
> 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 seems to bear out the concern expressed at _int_gist.c line 44:

/* XXX are we sure it's safe to scribble on the query object here? */

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Browne 2006-04-02 02:30:06 Re: Slony-I for circular replication
Previous Message Tom Lane 2006-04-02 00:37:14 Re: Suggestion: Which Binary?