Re: [HACKERS] WIP: long transactions on hot standby feedback replica/ proof of concept
От | Robert Haas |
---|---|
Тема | Re: [HACKERS] WIP: long transactions on hot standby feedback replica/ proof of concept |
Дата | |
Msg-id | CA+Tgmob+kYuTs4ZN26ZySYRMhuFCjK_OnVY8iTZHPdn7Ro2iYg@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 Tue, Oct 24, 2017 at 1:26 PM, Ivan Kartyshov <i.kartyshov@postgrespro.ru> wrote: > Hello. I made some bugfixes and rewrite the patch. I don't think it's a good idea to deliberately leave the state of the standby different from the state of the master on the theory that it won't matter. I feel like that's something that's likely to come back to bite us. Giving LockAcquireExtended() an argument that causes some AccessExclusiveLocks not all to be logged also seems pretty ugly, especially because there are no comments whatsoever explaining the rationale. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: