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

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-bugs(at)postgresql(dot)org
Cc: 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 12:58:22
Message-ID: 201012051358.22813.andres@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sunday 05 December 2010 13:29:35 Andres Freund wrote:
> On Sunday 05 December 2010 13:07:23 Martin Atukunda wrote:
> > > Due to the wonders of MVCC the old row is still available in the heap.
> > > Best read the docs about what MVCC means. And as pg's indexes don't
> > > care about visibility it will still try to index the "old" row.
> >
> > Thanks andreas,
> >
> > so, basically, the only way out of this would be to:
> >
> > 1. copy out all the rows
> > 2. truncate the Tables
> > 3. then create the index
> > 4. copy in the rows
>
> Something like:
>
> ALTER TABLE t ALTER apps TYPE text[];
> ALTER TABLE t ALTER apps TYPE bigint[] USING apps::bigint[];
On further thought the second one ought to be enough.

Andres

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2010-12-05 16:42:59 Re: BUG #5784: CREATE INDEX USING GIN complains about array containing null values yet none exist
Previous Message Andres Freund 2010-12-05 12:29:35 Re: BUG #5784: CREATE INDEX USING GIN complains about array containing null values yet none exist