Re: gist microvacuum doesn't appear to care about hot standby?

From: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>
Subject: Re: gist microvacuum doesn't appear to care about hot standby?
Date: 2018-12-13 04:28:30
Message-ID: CAPpHfds1FprKMQ+ViWMVeS8vY01knuV9tuZzizie4geTxrdXhg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 13, 2018 at 1:45 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> Is there any reason something like that isn't necessary for gist? If so,
> where's that documented? If not, uh, isn't that a somewhat serious bug
> in gist?

Thank you for pointing! This looks like a bug for me too. I'm going
to investigate more on this and provide a fix in next couple of days.

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-12-13 05:55:07 Re: Cache lookup errors with functions manipulation object addresses
Previous Message Michael Paquier 2018-12-13 03:22:58 Re: Making WAL receiver startup rely on GUC context for primary_conninfo and primary_slot_name