| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Vitaliy Gomenyuk <vgomenyuk(at)callfire(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>, Aleksandr Saraseka <asaraseka(at)callfire(dot)com> |
| Subject: | Re: BUG #14635: Query is executed slower on hot standby slave database then on master database |
| Date: | 2017-05-29 20:07:09 |
| Message-ID: | 28812.1496088429@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> But why can't the same mechanisms used on tables work on indexes, which is
> to wait out or conflict out any too-old transactions on the standby? Is
> there a fundamental reason for that, or just that no one got around to
> implementing it?
I think it's probably do-able, but not exactly trivial. The existing
behavior was an expedient solution when we were first getting hot standby
to work at all. Seems like it may be time to go back and improve it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniele Varrazzo | 2017-05-29 20:38:18 | [PATCH] Fixed malformed error message on malformed SCRAM message. |
| Previous Message | lsichello | 2017-05-29 20:01:53 | BUG #14677: BLOCKER: Postgres 9.4.12 repos only presenting packages for RHEL7 |