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

help / color / mirror / Atom feed
From: Andres Freund <andres@anarazel.de>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Vladimir Borodin <root@simply.name>
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: Tue, 3 Nov 2015 09:38:42 +0100
Message-ID: <20151103083842.GQ11897@awork2.anarazel.de> (raw)
In-Reply-To: <CA+TgmoamGeAtziNP1KtAuVxM8GHhog0ZOdrrvjNErnfEuqfBsA@mail.gmail.com>
References: <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>
	<95FD0B1A-7BD1-4CCE-86D4-2DF2B2AE2C68@simply.name>
	<CA+TgmoamGeAtziNP1KtAuVxM8GHhog0ZOdrrvjNErnfEuqfBsA@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On 2015-11-02 15:37:57 -0500, Robert Haas wrote:
> On Fri, Oct 30, 2015 at 9:49 AM, Vladimir Borodin <root@simply.name> wrote:
> > 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
> 
> Hmm.  That behavior seems unexpected to me, but I might be missing something.

The conflict is because of a relation lock, not because of
visibility. Hot-Standby feedback changes nothing about that.

I presume all the other conflicts are all because of relation level
locks? Check pg_stat_database_conflicts and the server logs to verify.

Andres


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (19+ messages)  latest in thread

Message-ID: <20151103083842.GQ11897@awork2.anarazel.de>
Permalink:  ../20151103083842.GQ11897@awork2.anarazel.de/
Also on:    postgresql.org/message-id/20151103083842.GQ11897@awork2.anarazel.de

 · 

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: andres@anarazel.de, robertmhaas@gmail.com, root@simply.name, alexk@hintbits.com, michael.paquier@gmail.com, pgsql-hackers@postgresql.org
  Subject: Re: [ADMIN] Replication slots and isolation levels
  In-Reply-To: <20151103083842.GQ11897@awork2.anarazel.de>

* 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