Re: [ADMIN] Replication slots and isolation levels
| От | Vladimir Borodin |
|---|---|
| Тема | Re: [ADMIN] Replication slots and isolation levels |
| Дата | |
| Msg-id | 52570F37-5C6E-40F9-A2E3-01858705B3E8@simply.name обсуждение исходный текст |
| Ответ на | Re: [ADMIN] Replication slots and isolation levels (Michael Paquier <michael.paquier@gmail.com>) |
| Ответы |
Re: [ADMIN] Replication slots and isolation levels
|
| Список | pgsql-hackers |
29 окт. 2015 г., в 13:12, Michael Paquier <michael.paquier@gmail.com> написал(а):On Thu, Oct 29, 2015 at 9:42 AM, Vladimir Borodin wrote:I’m wondering why do I get conflicts with recovery on hot standby using
replication slots and read commited isolation level? And if I start
repeatable read transaction I don’t get any errors. Below is some
diagnostics.
In the case of repeatable read the standby will wait before applying
the VACUUM WAL record cleaning up a relation page. Hence you won't get
conflicts in this case.
Standby will receive but will not apply? Or master will not vacuum needed by standby pages? It seems that the second one is happening because replication lag on standby does not increase while issuing such repeatable read transaction.
--
Michael
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
В списке pgsql-hackers по дате отправления: