Re: BUG #5784: CREATE INDEX USING GIN complains about array containing null values yet none exist

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-bugs(at)postgresql(dot)org, Martin Atukunda <matlads(at)gmail(dot)com>
Subject: Re: BUG #5784: CREATE INDEX USING GIN complains about array containing null values yet none exist
Date: 2010-12-05 16:42:59
Message-ID: 26122.1291567379@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Andres Freund <andres(at)anarazel(dot)de> writes:
>> On Sunday 05 December 2010 13:07:23 Martin Atukunda wrote:
>>>> so, basically, the only way out of this would be to:

I think the reason the given example fails is just that it's all being
done in one transaction. If the null-containing row were known dead
it wouldn't get indexed. So: commit.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2010-12-05 17:06:20 Re: BUG #5784: CREATE INDEX USING GIN complains about array containing null values yet none exist
Previous Message Andres Freund 2010-12-05 12:58:22 Re: BUG #5784: CREATE INDEX USING GIN complains about array containing null values yet none exist