Re: BUG #6307: intarray extention gin index does not work with Hot standby - Mailing list pgsql-bugs

From Maxim Boguk
Subject Re: BUG #6307: intarray extention gin index does not work with Hot standby
Date
Msg-id CAK-MWwRhuTDKyxHJU0Vk1w9M+WmUQ2iDY4rdMxvZr46NBtFW9Q@mail.gmail.com
Whole thread Raw
In response to Re: BUG #6307: intarray extention gin index does not work with Hot standby  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: BUG #6307: intarray extention gin index does not work with Hot standby  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Fri, Nov 25, 2011 at 11:17 PM, Simon Riggs <simon@2ndquadrant.com> wrote:

> On Thu, Nov 24, 2011 at 11:12 PM, Maksym Boguk <maxim.boguk@gmail.com>
> wrote:
>
> > postgres=# SELECT * from test where sections && '{2000}';
> >  id | sections
> > ----+----------
> > (0 rows)
> >
> > Ooops.
>
> Can you see if this is just intarray or if there are other failing cases?
>
> It would be good to get more info on this before I start investigating.
> Thanks
>

I know GIST on intarray[] do not have that problem.
Very likely the problem is limited to intarray[] GIN indexes only
(but I going to test some other not-well known GIN indexes tomorrow).

Broken FTS indexes on Hot Standby should be known years before.
And I never heard such reports.

pgsql-bugs by date:

Previous
From: Simon Riggs
Date:
Subject: Re: BUG #6307: intarray extention gin index does not work with Hot standby
Next
From: Tom Lane
Date:
Subject: Re: BUG #6307: intarray extention gin index does not work with Hot standby