Re: Relation cache invalidation on replica

From: Васильев Дмитрий <d(dot)vasilyev(at)postgrespro(dot)ru>
To: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Relation cache invalidation on replica
Date: 2016-02-26 13:44:54
Message-ID: CAB-SwXaOhg=bhNHgd5YBzprYaZ+m0wWEJkqGjrKE=WDEJh=OFg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

This is obviously a bug because without "concurrently" create index this do
not reproduce.

---
Dmitry Vasilyev
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company

2016-02-26 16:36 GMT+03:00 Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>:

> On Fri, Feb 26, 2016 at 3:41 PM, Васильев Дмитрий <
> d(dot)vasilyev(at)postgrespro(dot)ru> wrote:
>
>> Session opened on replica doesn't see concurrently created indexes at
>> this time on master.
>>
>
> As I get, on standby index is visible when you run SQL queries on catalog
> tables (that is what \d+ does), but planner doesn't pick it. Assuming that
> in new session planner picks this index, it seems to be bug for me.
>
> ------
> Alexander Korotkov
> Postgres Professional: http://www.postgrespro.com
> The Russian Postgres Company
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleg Bartunov 2016-02-26 13:51:42 Re: The plan for FDW-based sharding
Previous Message Alexander Korotkov 2016-02-26 13:36:17 Re: Relation cache invalidation on replica