| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | Ivan Kartyshov <i(dot)kartyshov(at)postgrespro(dot)ru> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] WIP: long transactions on hot standby feedback replica / proof of concept |
| Date: | 2018-08-14 09:04:42 |
| Message-ID: | CAD21AoCka6choPcPAXp7J51jC3P7Po-4ihxP0KHT+dBbzHpEjQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 28, 2018 at 11:24 PM, Ivan Kartyshov
<i(dot)kartyshov(at)postgrespro(dot)ru> wrote:
> Thank you for your valuable comments. I've made a few adjustments.
>
Thank you for working on this!
> The main goal of my changes is to let long read-only transactions run on
> replica if hot_standby_feedback is turned on.
FWIW the idea proposed on the thread[1], which allows us to disable
the heap truncation by vacuum per tables, might help this issue. Since
the original problem on that thread is a performance problem an
alternative proposal would be better, but I think the way would be
helpful for this issue too and is simple. A downside of that idea is
that there is additional work for user to configure the reloption to
each tables.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jarosław Torbicki | 2018-08-14 09:58:43 | Uncaught PHP Exception Doctrine\DBAL\Exception\UniqueConstraintViolationException: "An exception occurred while executing 'UPDATE |
| Previous Message | Fabien COELHO | 2018-08-14 09:03:16 | Re: libpq connection timeout mismanagement |