From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Simon Riggs <simon@2ndQuadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Hot Standby on git
Date: Fri, 09 Oct 2009 13:49:25 -0400
Message-ID: <4ACF77A5.1070706@enterprisedb.com> (raw)
In-Reply-To: <1253958559.4449.833.camel@ebony.2ndQuadrant>
References: <1253958559.4449.833.camel@ebony.2ndQuadrant>
While playing with conflict resolution, I bumped into this:
postgres=# begin ISOLATION LEVEL SERIALIZABLE;
BEGIN
postgres=# SELECT * FROM foo;
id | data
----+------
12 |
(1 row)
postgres=# SELECT * FROM foo;
id | data
----+------
12 |
(1 row)
postgres=# SELECT * FROM foo;
id | data
----+------
12 |
(1 row)
postgres=# SELECT * FROM foo;
id | data
----+------
12 |
(1 row)
postgres=# SELECT * FROM foo;
id | data
----+------
12 |
(1 row)
postgres=# SELECT * FROM foo;
ERROR: canceling statement due to conflict with recovery
postgres=# SELECT * FROM foo;
id | data
----+------
13 |
(1 row)
postgres=# SELECT * FROM foo;
id | data
----+------
13 |
(1 row)
postgres=# begin ISOLATION LEVEL SERIALIZABLE;
id | data
----+------
13 |
(1 row)
postgres=# SELECT * FROM foo;
BEGIN
postgres=# SELECT * FROM foo;
id | data
----+------
13 |
(1 row)
The backend and the frontend seem to go out of sync, when a conflict
happens in idle-in-transaction mode.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
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-hackers@postgresql.org
Cc: heikki.linnakangas@enterprisedb.com, simon@2ndQuadrant.com
Subject: Re: Hot Standby on git
In-Reply-To: <4ACF77A5.1070706@enterprisedb.com>
* 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