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

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

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com>, 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-28 07:02:37
Message-ID: CA+U5nM+stFo=f_iguAKC=H0+oaTOkK1v4wGJHPop4WtFw6cUFg@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Fri, Nov 25, 2011 at 6:33 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com> writes:
>> 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.
>
> You might think that, but you'd be wrong :-(.

Yes, that did sound ominous.

> ginRedoUpdateMetapage
> is failing to restore the contents of the pending-list correctly,
> which means this is broken for all types of GIN indexes.  Will fix.

Great detective work Tom as ever, much appreciated.

-- 
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

pgsql-bugs by date

Next:From: Thomas GoernerDate: 2011-11-28 12:26:26
Subject: Re: BUG #6308: Problem w. encoding in client
Previous:From: Kevin GrittnerDate: 2011-11-27 17:32:56
Subject: Re: BUG #6311: Performance degradation after upgrade

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