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

2010-12-05 Thread Andres Freund
Hi, On Sunday 05 December 2010 07:50:51 Martin Atukunda wrote: > > CREATE INDEX USING GIN complains about array containing null values yet > none exist. > > Take the following SQL as an example. > > -- >8 -- > > BEGIN; > CREATE TABLE t (id serial primary key, apps bigint[]); > INSERT INTO t (ap

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

2010-12-05 Thread Martin Atukunda
> 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

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

2010-12-05 Thread Andres Freund
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, > >

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

2010-12-05 Thread Andres Freund
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

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

2010-12-05 Thread Tom Lane
Andres Freund 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

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

2010-12-05 Thread Andres Freund
On Sunday 05 December 2010 17:42:59 Tom Lane wrote: > Andres Freund 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

Re: [BUGS] BUG #5783: plpythonu bool behavior change

2010-12-05 Thread Peter Eisentraut
On sön, 2010-12-05 at 00:25 +, Adrian Klaver wrote: > Seems there was a change in behavior for plpythonu with regards to > boolean fields from 8.4 to 9.0. Previously, setting a field inside a > plpythonu function to "f" would work, now that returns a 't' in the > database field. To get the 'f'

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

2010-12-05 Thread Tom Lane
Andres Freund writes: > On Sunday 05 December 2010 17:42:59 Tom Lane wrote: >> 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. > Um I doubt it. [ gets out gdb..

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

2010-12-05 Thread Martin Atukunda
On Sun, Dec 5, 2010 at 7:58 PM, Andres Freund wrote: > 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 MVC

Re: [BUGS] BUG #5783: plpythonu bool behavior change

2010-12-05 Thread Adrian Klaver
On Sunday 05 December 2010 9:10:06 am Peter Eisentraut wrote: > On sön, 2010-12-05 at 00:25 +, Adrian Klaver wrote: > > Seems there was a change in behavior for plpythonu with regards to > > boolean fields from 8.4 to 9.0. Previously, setting a field inside a > > plpythonu function to "f" would