Re: BUG #18118: bug report for COMMIT AND CHAIN feature

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: evan(dot)lx(at)alibaba-inc(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18118: bug report for COMMIT AND CHAIN feature
Date: 2023-09-21 06:41:20
Message-ID: a2b1d633e39041d57f6d43e9e14d9fd1877a5e1c.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2023-09-21 07:06:32 Re: group by true now errors with non-integer constant in GROUP BY
Previous Message PG Bug reporting form 2023-09-21 06:39:39 BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"