| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Vladimir Borodin <root(at)simply(dot)name> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [ADMIN] Replication slots and isolation levels |
| Date: | 2015-10-29 10:12:39 |
| Message-ID: | CAB7nPqTW_v4odZrRX7vYtf5OWVBwzK=oDffwikgrOunQFsa8JA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
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.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Borodin | 2015-10-29 10:33:18 | Re: [ADMIN] Replication slots and isolation levels |
| Previous Message | Vladimir Borodin | 2015-10-29 08:42:57 | Re: [ADMIN] Replication slots and isolation levels |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Borodin | 2015-10-29 10:33:18 | Re: [ADMIN] Replication slots and isolation levels |
| Previous Message | Amit Langote | 2015-10-29 10:05:03 | Re: Cross-check recent documentation changes |