Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZsA3R-0002ZF-My for pgsql-hackers@arkaria.postgresql.org; Fri, 30 Oct 2015 13:49:17 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZsA3R-0000Uc-5r for pgsql-hackers@arkaria.postgresql.org; Fri, 30 Oct 2015 13:49:17 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZsA3Q-0000UT-6R; Fri, 30 Oct 2015 13:49:16 +0000 Received: from forward17m.cmail.yandex.net ([5.255.216.148]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZsA3F-0003YZ-6w; Fri, 30 Oct 2015 13:49:15 +0000 Received: from smtp3m.mail.yandex.net (smtp3m.mail.yandex.net [IPv6:2a02:6b8:0:2519::125]) by forward17m.cmail.yandex.net (Yandex) with ESMTP id D1F6020ECB; Fri, 30 Oct 2015 16:49:01 +0300 (MSK) Received: from smtp3m.mail.yandex.net (localhost [127.0.0.1]) by smtp3m.mail.yandex.net (Yandex) with ESMTP id EA9BA27A0051; Fri, 30 Oct 2015 16:49:00 +0300 (MSK) Received: by smtp3m.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 6RFpCdYXFI-n01aqGF8; Fri, 30 Oct 2015 16:49:00 +0300 (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=simply.name; s=mail; t=1446212940; bh=GSuZ7WFzeagaRPG1JopHbBWoWTiGmKHm+7FwyyYs7p8=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Message-Id:References:To:X-Mailer; b=s/Y+ct1BUcPHwSDgxJGBSoMUQt81Lr0jx6M8WAjQ5eW24qf/P15MA0y9lDTFcbxrB HVfjfloLKRggYj3kP4d7eLOO9VXRlQqB1OqyVlVCucvw12jsDCmGwxdVqn9mwGjHo8 yGkZaujO/JGkp/qw3Z+uclY0NSh/QSa+DYG9bOb8= Authentication-Results: smtp3m.mail.yandex.net; dkim=pass header.i=@simply.name X-Yandex-ForeignMX: US Content-Type: multipart/alternative; boundary="Apple-Mail=_EE9D29B6-BE0F-441E-879D-CE034B4F1057" Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: [ADMIN] Replication slots and isolation levels From: Vladimir Borodin In-Reply-To: Date: Fri, 30 Oct 2015 16:49:00 +0300 Cc: Oleksii Kliukin , Michael Paquier , pgsql-admin , PostgreSQL-development Message-Id: <95FD0B1A-7BD1-4CCE-86D4-2DF2B2AE2C68@simply.name> References: <7F74C5EA-6741-44FC-B6C6-E96F18D761FB@simply.name> <52570F37-5C6E-40F9-A2E3-01858705B3E8@simply.name> <0E6700E4-195C-450D-A051-D19F92B2A9D7@simply.name> <86D2C6D2-C332-4BF9-A82E-C9F7FA471712@simply.name> <088B276D-4073-4582-82D4-08F50E43B426@simply.name> To: Robert Haas X-Mailer: Apple Mail (2.2104) X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org --Apple-Mail=_EE9D29B6-BE0F-441E-879D-CE034B4F1057 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > 30 =D0=BE=D0=BA=D1=82. 2015 =D0=B3., =D0=B2 16:04, Robert Haas = =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0)= : >=20 > On Fri, Oct 30, 2015 at 12:40 PM, Vladimir Borodin = wrote: >> I still don=E2=80=99t 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=E2=80=99t the = documentation mention that >> using READ COMMITED (which is the default) you may still get = conflicts with >> recovery while using replication slots? >=20 > Are you doing BEGIN / one or more SELECT statements / END? >=20 > Or just a bare SELECT with no explicit transaction control? I=E2=80=99ve 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 >=20 > --=20 > Robert Haas > EnterpriseDB: http://www.enterprisedb.com > The Enterprise PostgreSQL Company >=20 >=20 > --=20 > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin -- =D0=94=D0=B0 =D0=BF=D1=80=D0=B5=D0=B1=D1=83=D0=B4=D0=B5=D1=82 =D1=81 = =D0=B2=D0=B0=D0=BC=D0=B8 =D1=81=D0=B8=D0=BB=D0=B0=E2=80=A6 https://simply.name/ru --Apple-Mail=_EE9D29B6-BE0F-441E-879D-CE034B4F1057 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
30 =D0=BE=D0=BA=D1=82. 2015 =D0=B3., =D0=B2 16:04, Robert = Haas <robertmhaas@gmail.com> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0= =B0=D0=BB(=D0=B0):

On Fri, Oct 30, 2015 at 12:40 PM, Vladimir Borodin <root@simply.name> = wrote:
I still = don=E2=80=99t 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=E2=80=99t 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=E2=80=99ve = 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.



--
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


--
=D0=94=D0=B0 =D0=BF=D1=80=D0=B5=D0=B1=D1=83=D0=B4=D0=B5=D1=82 = =D1=81 =D0=B2=D0=B0=D0=BC=D0=B8 =D1=81=D0=B8=D0=BB=D0=B0=E2=80=A6
https://simply.name/ru

= --Apple-Mail=_EE9D29B6-BE0F-441E-879D-CE034B4F1057--