From: | Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 21:54:30 |
Message-ID: | CAK-MWwSiiBbmJ=+TPbJSB1X-5pR0vw49VGrJMGVBY=+8Dbf0KQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Nov 28, 2011 at 6:02 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> 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.
>
>
Thank you very much.
Is that fix will be included to the next minor versions releases?
(especially into 9.1.2)?
--
Maxim Boguk
Senior Postgresql DBA.
From | Date | Subject | |
---|---|---|---|
Next Message | David Schnur | 2011-11-28 22:20:42 | Re: Repeatable crash in pg_dump (with -d2 info) |
Previous Message | Phil Sorber | 2011-11-28 21:14:41 | Re: objects tied to missing extension |