| From: | Victor Yegorov <vyegorov(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Relation cache invalidation on replica |
| Date: | 2017-04-19 14:07:49 |
| Message-ID: | CAGnEbogjOh57Pf6MvpDWirW=5Q=UgH5-eDztbrxhPp51LWwM7w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2017-03-13 9:22 GMT+02:00 Andres Freund <andres(at)anarazel(dot)de>:
> >I think we're hitting this particular issue quite frequently when
> >rebuilding indexes on master after big-volume data manipulations.
> >
> >We have `pgbouncer` in transaction mode for both, master and slave,
> >therefore it's quite typical to have sessions on slave, that
> >were using indexes before those we're re-created. Sad, but right now
> >maintenance is a big performance hit for our applications,
> >we have to re-connect them to start using indexes again.
> >
> >Are there any chances to get fix for this issue released in 10.0 and,
> >perhaps, backpatched also?
>
> I'm not at my computer right now, but I recall committing something like
> my approach.
Andres, can you point me on the commit you're mentioning, please?
--
Victor Yegorov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Remi Colinet | 2017-04-19 14:13:56 | Re: [PATCH] New command to monitor progression of long running queries |
| Previous Message | Andrew Dunstan | 2017-04-19 13:59:29 | BuildFarm client release 4.19 |