From: Laurenz Albe <laurenz.albe@cybertec.at>
To: evan.lx@alibaba-inc.com
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18118: bug report for COMMIT AND CHAIN feature
Date: Thu, 21 Sep 2023 08:41:20 +0200
Message-ID: <a2b1d633e39041d57f6d43e9e14d9fd1877a5e1c.camel@cybertec.at> (raw)
In-Reply-To: <18118-4b72fcbb903aace6@postgresql.org>
References: <18118-4b72fcbb903aace6@postgresql.org>
On Wed, 2023-09-20 at 09:31 +0000, PG Bug reporting form wrote:
> PostgreSQL version: 14.9
> Operating system: centos7
> Description:
>
> COMMIT(280a408b48d5ee42969f981bceb9e9426c3a344c) provides a way to support
> chained commits. During recent development, I found that it left a flaw.
>
> The defect can be reproduced as follows:
>
> START TRANSACTION ISOLATION LEVEL SERIALIZABLE; COMMIT;
> START TRANSACTION ISOLATION LEVEL REPEATABLE READ\; savepoint s\; COMMIT AND
> CHAIN;
> SHOW transaction_isolation; -- transaction is active at this point
> COMMIT;
>
> will get:
> postgres=*# SHOW transaction_isolation; -- transaction is active at this
> point
> transaction_isolation
> -----------------------
> serializable
> (1 row)
I tried to reproduce that and failed, both with v14 and v16.
For me, "transaction_isolation" is "repeatable read".
Yours,
Laurenz Albe
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-bugs@postgresql.org
Cc: laurenz.albe@cybertec.at, evan.lx@alibaba-inc.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18118: bug report for COMMIT AND CHAIN feature
In-Reply-To: <a2b1d633e39041d57f6d43e9e14d9fd1877a5e1c.camel@cybertec.at>
* 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