Re: [HACKERS] WIP: long transactions on hot standby feedback replica/ proof of concept
От | Masahiko Sawada |
---|---|
Тема | Re: [HACKERS] WIP: long transactions on hot standby feedback replica/ proof of concept |
Дата | |
Msg-id | CAD21AoCka6choPcPAXp7J51jC3P7Po-4ihxP0KHT+dBbzHpEjQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] WIP: long transactions on hot standby feedback replica/ proof of concept (Ivan Kartyshov <i.kartyshov@postgrespro.ru>) |
Ответы |
Re: [HACKERS] WIP: long transactions on hot standby feedback replica/ proof of concept
|
Список | pgsql-hackers |
On Wed, Feb 28, 2018 at 11:24 PM, Ivan Kartyshov <i.kartyshov@postgrespro.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. [1] https://www.postgresql.org/message-id/CAHGQGwE5UqFqSq1%3DkV3QtTUtXphTdyHA-8rAj4A%3DY%2Be4kyp3BQ%40mail.gmail.com Regards, -- Masahiko Sawada NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
В списке pgsql-hackers по дате отправления: