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

Re: BUG #6307: intarray extention gin index does not work with Hot standby

From: Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #6307: intarray extention gin index does not work with Hot standby
Date: 2011-11-25 12:46:47
Message-ID: CAK-MWwRhuTDKyxHJU0Vk1w9M+WmUQ2iDY4rdMxvZr46NBtFW9Q@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Fri, Nov 25, 2011 at 11:17 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:

> On Thu, Nov 24, 2011 at 11:12 PM, Maksym Boguk <maxim(dot)boguk(at)gmail(dot)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.

In response to

Responses

pgsql-bugs by date

Next:From: Andrew MilneDate: 2011-11-25 12:51:51
Subject: BUG #6309: ECPG pre-processor issue
Previous:From: Thomas GoernerDate: 2011-11-25 12:21:45
Subject: BUG #6308: Problem w. encoding in client

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