| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Oleksii Kliukin <alexk(at)hintbits(dot)com> |
| Cc: | Vladimir Borodin <root(at)simply(dot)name>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Replication slots and isolation levels |
| Date: | 2015-10-30 11:30:04 |
| Message-ID: | CA+TgmoZzi8-72PksOf8NDBz8nGU97NH_VUgNybxyB_5U_tBBCg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
On Thu, Oct 29, 2015 at 3:29 PM, Oleksii Kliukin <alexk(at)hintbits(dot)com> wrote:
> Could it be a consequence of how REPEATABLE READ transactions handle
> snapshots? With REPEATABLE READ the snapshot is acquired only once at the
> beginning of a transaction; a READ COMMITTED transaction re-evaluates its
> snapshot with each new command.
I bet that's exactly it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Borodin | 2015-10-30 11:40:23 | Re: [HACKERS] Replication slots and isolation levels |
| Previous Message | Jerry Sievers | 2015-10-29 18:28:02 | Re: PITR using pg_basebackup ERROR |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Borodin | 2015-10-30 11:40:23 | Re: [HACKERS] Replication slots and isolation levels |
| Previous Message | Robert Haas | 2015-10-30 11:26:35 | Re: security_barrier view option type mistake in create view document |