Skip site navigation (1) Skip section navigation (2)

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

From: Martin Atukunda <matlads(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5784: CREATE INDEX USING GIN complains about array containing null values yet none exist
Date: 2010-12-05 12:07:23
Message-ID: AANLkTikSHA0CvwZsQLNFUXCBVELEmXG_bPCqTnHqwXEN@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
> 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

- Martin -

In response to

Responses

pgsql-bugs by date

Next:From: Andres FreundDate: 2010-12-05 12:29:35
Subject: Re: BUG #5784: CREATE INDEX USING GIN complains about array containing null values yet none exist
Previous:From: Andres FreundDate: 2010-12-05 11:39:23
Subject: Re: BUG #5784: CREATE INDEX USING GIN complains about array containing null values yet none exist

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group