pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Vladimir Borodin <root@simply.name>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Oleksii Kliukin <alexk@hintbits.com>
Cc: Michael Paquier <michael.paquier@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [ADMIN] Replication slots and isolation levels
Date: Fri, 30 Oct 2015 16:49:00 +0300
Message-ID: <95FD0B1A-7BD1-4CCE-86D4-2DF2B2AE2C68@simply.name> (raw)
In-Reply-To: <CA+TgmoYn=Myxu9QHBHzwZmQtsHn=GYCix6O+LNyHxQrgP86T8w@mail.gmail.com>
References: <7F74C5EA-6741-44FC-B6C6-E96F18D761FB@simply.name>
	<BE95C564-0D49-462A-A57C-4C9DF6238F71@simply.name>
	<CAB7nPqTW_v4odZrRX7vYtf5OWVBwzK=oDffwikgrOunQFsa8JA@mail.gmail.com>
	<52570F37-5C6E-40F9-A2E3-01858705B3E8@simply.name>
	<CAB7nPqQZAqvwpJ3eQ0BXGdw26fjNuKXXGHijvdahVXreNbsASA@mail.gmail.com>
	<0E6700E4-195C-450D-A051-D19F92B2A9D7@simply.name>
	<CAB7nPqTSVXR1WQegikpnkATjR3oz8FQE3hUf9RUk+o9VN0+zrQ@mail.gmail.com>
	<86D2C6D2-C332-4BF9-A82E-C9F7FA471712@simply.name>
	<B0D38B8D-C174-44EE-9F84-31B8EE68AA8C@hintbits.com>
	<CA+TgmoZzi8-72PksOf8NDBz8nGU97NH_VUgNybxyB_5U_tBBCg@mail.gmail.com>
	<088B276D-4073-4582-82D4-08F50E43B426@simply.name>
	<CA+TgmoYn=Myxu9QHBHzwZmQtsHn=GYCix6O+LNyHxQrgP86T8w@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>


> 30 окт. 2015 г., в 16:04, Robert Haas <robertmhaas@gmail.com> написал(а):
> 
> On Fri, Oct 30, 2015 at 12:40 PM, Vladimir Borodin <root@simply.name> wrote:
>> I still don’t fully understand why is it so (the problem occurs while
>> running only one SELECT-statement in READ COMMITED so only one snapshot is
>> taken), but if is expected behavior shouldn’t the documentation mention that
>> using READ COMMITED (which is the default) you may still get conflicts with
>> recovery while using replication slots?
> 
> Are you doing BEGIN / one or more SELECT statements / END?
> 
> Or just a bare SELECT with no explicit transaction control?

I’ve tried two ways - bare SELECT in autocommit mode and BEGIN; SELECT; ROLLBACK. I first described the problem in thread on pgsql-admin@ [0], there is copy-paste from psql there, but during conversation initial description was lost.

[0] http://www.postgresql.org/message-id/7F74C5EA-6741-44FC-B6C6-E96F18D761FB@simply.name

> 
> -- 
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
> 
> 
> -- 
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin


--
Да пребудет с вами сила…
https://simply.name/ru

view thread (19+ messages)  latest in thread

Message-ID: <95FD0B1A-7BD1-4CCE-86D4-2DF2B2AE2C68@simply.name>
Permalink:  ../95FD0B1A-7BD1-4CCE-86D4-2DF2B2AE2C68@simply.name/
Also on:    postgresql.org/message-id/95FD0B1A-7BD1-4CCE-86D4-2DF2B2AE2C68@simply.name

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: root@simply.name, robertmhaas@gmail.com, alexk@hintbits.com, michael.paquier@gmail.com, pgsql-hackers@postgresql.org
  Subject: Re: [ADMIN] Replication slots and isolation levels
  In-Reply-To: <95FD0B1A-7BD1-4CCE-86D4-2DF2B2AE2C68@simply.name>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox