pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #16867: savepoints vs. commit and chain
9+ messages / 4 participants
[nested] [flat]
Commits from this thread:
2021-02-19 fe06819f10 be7485a1e3 67b3ee2929 Fix psql's ON_ERROR_ROLLBACK so that it handles COMMIT AND CHAIN.
2021-02-19 8a55cb5ba9 422012c98f fadcc4e81b Fix bug in COMMIT AND CHAIN command.
* BUG #16867: savepoints vs. commit and chain
@ 2021-02-15 20:53 PG Bug reporting form <noreply@postgresql.org>
2021-02-15 21:47 ` Re: BUG #16867: savepoints vs. commit and chain Arthur Nascimento <tureba@gmail.com>
0 siblings, 1 reply; 9+ messages in thread
From: PG Bug reporting form @ 2021-02-15 20:53 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: tureba@gmail.com
The following bug has been logged on the website:
Bug reference: 16867
Logged by: Arthur Nascimento
Email address: tureba@gmail.com
PostgreSQL version: 13.2
Operating system: CentOS
Description:
Hi all,
I'm seeing an unexpected behavior when using savepoints along commit and
chain. I couldn't find a mention of it in the docs and the regression tests
seem to not cover it.
On a trivial transaction, I might do:
=# begin;
*=# commit and chain;
*=# -- In this point I'm inside a second transaction
However, if the first transaction contained any unreleased savepoints, the
chain does not get me to a second transaction:
=# begin;
*=# savepoint foo;
*=# commit and chain;
=# -- In this point I'm not inside a second transaction
I first noticed it when using psql's ON_ERROR_ROLLBACK, but it can be
reproduced without it, as shown above.
I also thought it might be psql's fault at not knowing that COMMIT can also
return the state PQTRANS_INTRANS in
https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/bin/psql/common.c;h=6f507104f464fde...
But even trying a local fix (by adding COMMIT to the possible commands) to
that didn't quite solve it, so there might be something else.
Let me know what I might be missing in this.
Thanks,
Arthur Nascimento
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: BUG #16867: savepoints vs. commit and chain
2021-02-15 20:53 BUG #16867: savepoints vs. commit and chain PG Bug reporting form <noreply@postgresql.org>
@ 2021-02-15 21:47 ` Arthur Nascimento <tureba@gmail.com>
2021-02-16 04:49 ` Re: BUG #16867: savepoints vs. commit and chain Fujii Masao <masao.fujii@oss.nttdata.com>
0 siblings, 1 reply; 9+ messages in thread
From: Arthur Nascimento @ 2021-02-15 21:47 UTC (permalink / raw)
To: Arthur Filipe Martins Nascimento <tureba@gmail.com>; pgsql-bugs@lists.postgresql.org
On Mon, 15 Feb 2021 at 17:54, PG Bug reporting form
<noreply@postgresql.org> wrote:
> On a trivial transaction, I might do:
>
> =# begin;
> *=# commit and chain;
> *=# -- In this point I'm inside a second transaction
I forgot to mention that this case also works as expected:
=# begin;
*=# savepoint foo;
*=# release foo;
*=# commit and chain;
*=# -- In this point I'm also inside a second transaction
So it's only the unmatched savepoint/release transactions that are an issue.
I also attached the change I did to psql locally. But since it didn't
solve the issue, it's mostly for curiosity's sake.
Thanks,
Tureba - Arthur Nascimento
Attachments:
psql-savepoint-cac.txt (text/plain, 924B) download
diff --git a/src/bin/psql/common.c b/src/bin/psql/common.c
index 6f507104f4..0ef9367ff3 100644
--- a/src/bin/psql/common.c
+++ b/src/bin/psql/common.c
@@ -1350,12 +1350,13 @@ SendQuery(const char *query)
/*
* Do nothing if they are messing with savepoints themselves:
- * If the user did RELEASE or ROLLBACK, our savepoint is gone.
- * If they issued a SAVEPOINT, releasing ours would remove
- * theirs.
+ * If the user did COMMIT AND CHAIN, RELEASE or ROLLBACK,
+ * our savepoint is gone. If they issued a SAVEPOINT,
+ * releasing ours would remove theirs.
*/
if (results &&
- (strcmp(PQcmdStatus(results), "SAVEPOINT") == 0 ||
+ (strcmp(PQcmdStatus(results), "COMMIT") == 0 ||
+ strcmp(PQcmdStatus(results), "SAVEPOINT") == 0 ||
strcmp(PQcmdStatus(results), "RELEASE") == 0 ||
strcmp(PQcmdStatus(results), "ROLLBACK") == 0))
svptcmd = NULL;
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: BUG #16867: savepoints vs. commit and chain
2021-02-15 20:53 BUG #16867: savepoints vs. commit and chain PG Bug reporting form <noreply@postgresql.org>
2021-02-15 21:47 ` Re: BUG #16867: savepoints vs. commit and chain Arthur Nascimento <tureba@gmail.com>
@ 2021-02-16 04:49 ` Fujii Masao <masao.fujii@oss.nttdata.com>
2021-02-16 18:03 ` Re: BUG #16867: savepoints vs. commit and chain Arthur Nascimento <tureba@gmail.com>
0 siblings, 1 reply; 9+ messages in thread
From: Fujii Masao @ 2021-02-16 04:49 UTC (permalink / raw)
To: Arthur Nascimento <tureba@gmail.com>; pgsql-bugs@lists.postgresql.org
On 2021/02/16 6:47, Arthur Nascimento wrote:
> On Mon, 15 Feb 2021 at 17:54, PG Bug reporting form
> <noreply@postgresql.org> wrote:
>> On a trivial transaction, I might do:
>>
>> =# begin;
>> *=# commit and chain;
>> *=# -- In this point I'm inside a second transaction
>
> I forgot to mention that this case also works as expected:
>
> =# begin;
> *=# savepoint foo;
> *=# release foo;
> *=# commit and chain;
> *=# -- In this point I'm also inside a second transaction
>
> So it's only the unmatched savepoint/release transactions that are an issue.
>
> I also attached the change I did to psql locally.
LGTM.
> But since it didn't
> solve the issue, it's mostly for curiosity's sake.
In the server side, ISTM that CommitTransactionCommand() needs to handle
the COMMIT AND CHAIN in TBLOCK_SUBCOMMIT case, but it forgot to do that.
Patch attached. I'm not sure if this is a bug or an intentional behavior.
Probably we need to look at the past discussion about AND CHAIN feature.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
Attachments:
savepoint_and_chain.patch (text/plain, 2.5K) download
diff --git a/src/backend/access/transam/xact.c b/src/backend/access/transam/xact.c
index 17fbc41bbb..4e6a3df6b8 100644
--- a/src/backend/access/transam/xact.c
+++ b/src/backend/access/transam/xact.c
@@ -3105,6 +3105,13 @@ CommitTransactionCommand(void)
Assert(s->parent == NULL);
CommitTransaction();
s->blockState = TBLOCK_DEFAULT;
+ if (s->chain)
+ {
+ StartTransaction();
+ s->blockState = TBLOCK_INPROGRESS;
+ s->chain = false;
+ RestoreTransactionCharacteristics();
+ }
}
else if (s->blockState == TBLOCK_PREPARE)
{
diff --git a/src/test/regress/expected/transactions.out b/src/test/regress/expected/transactions.out
index 1b03310029..75dc6558d8 100644
--- a/src/test/regress/expected/transactions.out
+++ b/src/test/regress/expected/transactions.out
@@ -774,6 +774,46 @@ SHOW transaction_deferrable;
(1 row)
INSERT INTO abc VALUES (5);
+COMMIT;
+START TRANSACTION ISOLATION LEVEL REPEATABLE READ, READ WRITE, DEFERRABLE;
+SHOW transaction_isolation;
+ transaction_isolation
+-----------------------
+ repeatable read
+(1 row)
+
+SHOW transaction_read_only;
+ transaction_read_only
+-----------------------
+ off
+(1 row)
+
+SHOW transaction_deferrable;
+ transaction_deferrable
+------------------------
+ on
+(1 row)
+
+SAVEPOINT x;
+COMMIT AND CHAIN; -- TBLOCK_SUBCOMMIT
+SHOW transaction_isolation;
+ transaction_isolation
+-----------------------
+ repeatable read
+(1 row)
+
+SHOW transaction_read_only;
+ transaction_read_only
+-----------------------
+ off
+(1 row)
+
+SHOW transaction_deferrable;
+ transaction_deferrable
+------------------------
+ on
+(1 row)
+
COMMIT;
-- different mix of options just for fun
START TRANSACTION ISOLATION LEVEL SERIALIZABLE, READ WRITE, NOT DEFERRABLE;
diff --git a/src/test/regress/sql/transactions.sql b/src/test/regress/sql/transactions.sql
index bf1016489d..d1b6ed0280 100644
--- a/src/test/regress/sql/transactions.sql
+++ b/src/test/regress/sql/transactions.sql
@@ -458,6 +458,17 @@ SHOW transaction_deferrable;
INSERT INTO abc VALUES (5);
COMMIT;
+START TRANSACTION ISOLATION LEVEL REPEATABLE READ, READ WRITE, DEFERRABLE;
+SHOW transaction_isolation;
+SHOW transaction_read_only;
+SHOW transaction_deferrable;
+SAVEPOINT x;
+COMMIT AND CHAIN; -- TBLOCK_SUBCOMMIT
+SHOW transaction_isolation;
+SHOW transaction_read_only;
+SHOW transaction_deferrable;
+COMMIT;
+
-- different mix of options just for fun
START TRANSACTION ISOLATION LEVEL SERIALIZABLE, READ WRITE, NOT DEFERRABLE;
SHOW transaction_isolation;
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: BUG #16867: savepoints vs. commit and chain
2021-02-15 20:53 BUG #16867: savepoints vs. commit and chain PG Bug reporting form <noreply@postgresql.org>
2021-02-15 21:47 ` Re: BUG #16867: savepoints vs. commit and chain Arthur Nascimento <tureba@gmail.com>
2021-02-16 04:49 ` Re: BUG #16867: savepoints vs. commit and chain Fujii Masao <masao.fujii@oss.nttdata.com>
@ 2021-02-16 18:03 ` Arthur Nascimento <tureba@gmail.com>
2021-02-18 13:58 ` Re: BUG #16867: savepoints vs. commit and chain Fujii Masao <masao.fujii@oss.nttdata.com>
0 siblings, 1 reply; 9+ messages in thread
From: Arthur Nascimento @ 2021-02-16 18:03 UTC (permalink / raw)
To: Fujii Masao <masao.fujii@oss.nttdata.com>; +Cc: pgsql-bugs@lists.postgresql.org
Hi, Fujii-san,
On Tue, 16 Feb 2021 at 01:49, Fujii Masao <masao.fujii@oss.nttdata.com> wrote:
> In the server side, ISTM that CommitTransactionCommand() needs to handle
> the COMMIT AND CHAIN in TBLOCK_SUBCOMMIT case, but it forgot to do that.
> Patch attached. I'm not sure if this is a bug or an intentional behavior.
> Probably we need to look at the past discussion about AND CHAIN feature.
I can confirm that your patch solved it for me. Thanks for looking into it.
Tureba - Arthur Nascimento
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: BUG #16867: savepoints vs. commit and chain
2021-02-15 20:53 BUG #16867: savepoints vs. commit and chain PG Bug reporting form <noreply@postgresql.org>
2021-02-15 21:47 ` Re: BUG #16867: savepoints vs. commit and chain Arthur Nascimento <tureba@gmail.com>
2021-02-16 04:49 ` Re: BUG #16867: savepoints vs. commit and chain Fujii Masao <masao.fujii@oss.nttdata.com>
2021-02-16 18:03 ` Re: BUG #16867: savepoints vs. commit and chain Arthur Nascimento <tureba@gmail.com>
@ 2021-02-18 13:58 ` Fujii Masao <masao.fujii@oss.nttdata.com>
2021-02-18 14:10 ` Re: BUG #16867: savepoints vs. commit and chain Vik Fearing <vik@postgresfriends.org>
0 siblings, 1 reply; 9+ messages in thread
From: Fujii Masao @ 2021-02-18 13:58 UTC (permalink / raw)
To: Arthur Nascimento <tureba@gmail.com>; +Cc: pgsql-bugs@lists.postgresql.org
On 2021/02/17 3:03, Arthur Nascimento wrote:
> Hi, Fujii-san,
>
> On Tue, 16 Feb 2021 at 01:49, Fujii Masao <masao.fujii@oss.nttdata.com> wrote:
>> In the server side, ISTM that CommitTransactionCommand() needs to handle
>> the COMMIT AND CHAIN in TBLOCK_SUBCOMMIT case, but it forgot to do that.
>> Patch attached. I'm not sure if this is a bug or an intentional behavior.
>> Probably we need to look at the past discussion about AND CHAIN feature.
>
> I can confirm that your patch solved it for me. Thanks for looking into it.
Thanks for testing the patch!
As far as I read the past discussion about chain transaction,
I could not find any mention that current behavior that you reported
is intentional.
Barring any objection, I will commit the patch that you wrote
for psql and the patch I wrote.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: BUG #16867: savepoints vs. commit and chain
2021-02-15 20:53 BUG #16867: savepoints vs. commit and chain PG Bug reporting form <noreply@postgresql.org>
2021-02-15 21:47 ` Re: BUG #16867: savepoints vs. commit and chain Arthur Nascimento <tureba@gmail.com>
2021-02-16 04:49 ` Re: BUG #16867: savepoints vs. commit and chain Fujii Masao <masao.fujii@oss.nttdata.com>
2021-02-16 18:03 ` Re: BUG #16867: savepoints vs. commit and chain Arthur Nascimento <tureba@gmail.com>
2021-02-18 13:58 ` Re: BUG #16867: savepoints vs. commit and chain Fujii Masao <masao.fujii@oss.nttdata.com>
@ 2021-02-18 14:10 ` Vik Fearing <vik@postgresfriends.org>
2021-02-19 04:02 ` Re: BUG #16867: savepoints vs. commit and chain Fujii Masao <masao.fujii@oss.nttdata.com>
0 siblings, 1 reply; 9+ messages in thread
From: Vik Fearing @ 2021-02-18 14:10 UTC (permalink / raw)
To: Fujii Masao <masao.fujii@oss.nttdata.com>; Arthur Nascimento <tureba@gmail.com>; +Cc: pgsql-bugs@lists.postgresql.org
On 2/18/21 2:58 PM, Fujii Masao wrote:
>
>
> On 2021/02/17 3:03, Arthur Nascimento wrote:
>> Hi, Fujii-san,
>>
>> On Tue, 16 Feb 2021 at 01:49, Fujii Masao
>> <masao.fujii@oss.nttdata.com> wrote:
>>> In the server side, ISTM that CommitTransactionCommand() needs to handle
>>> the COMMIT AND CHAIN in TBLOCK_SUBCOMMIT case, but it forgot to do that.
>>> Patch attached. I'm not sure if this is a bug or an intentional
>>> behavior.
>>> Probably we need to look at the past discussion about AND CHAIN feature.
>>
>> I can confirm that your patch solved it for me. Thanks for looking
>> into it.
>
> Thanks for testing the patch!
>
> As far as I read the past discussion about chain transaction,
> I could not find any mention that current behavior that you reported
> is intentional.
>
> Barring any objection, I will commit the patch that you wrote
> for psql and the patch I wrote.
No objection from me. According to the standard, a COMMIT should
destroy all savepoints and terminate the transaction, even if AND CHAIN
is specified.
--
Vik Fearing
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: BUG #16867: savepoints vs. commit and chain
2021-02-15 20:53 BUG #16867: savepoints vs. commit and chain PG Bug reporting form <noreply@postgresql.org>
2021-02-15 21:47 ` Re: BUG #16867: savepoints vs. commit and chain Arthur Nascimento <tureba@gmail.com>
2021-02-16 04:49 ` Re: BUG #16867: savepoints vs. commit and chain Fujii Masao <masao.fujii@oss.nttdata.com>
2021-02-16 18:03 ` Re: BUG #16867: savepoints vs. commit and chain Arthur Nascimento <tureba@gmail.com>
2021-02-18 13:58 ` Re: BUG #16867: savepoints vs. commit and chain Fujii Masao <masao.fujii@oss.nttdata.com>
2021-02-18 14:10 ` Re: BUG #16867: savepoints vs. commit and chain Vik Fearing <vik@postgresfriends.org>
@ 2021-02-19 04:02 ` Fujii Masao <masao.fujii@oss.nttdata.com>
2021-02-19 08:29 ` Re: BUG #16867: savepoints vs. commit and chain Vik Fearing <vik@postgresfriends.org>
0 siblings, 1 reply; 9+ messages in thread
From: Fujii Masao @ 2021-02-19 04:02 UTC (permalink / raw)
To: Vik Fearing <vik@postgresfriends.org>; Arthur Nascimento <tureba@gmail.com>; +Cc: pgsql-bugs@lists.postgresql.org
On 2021/02/18 23:10, Vik Fearing wrote:
> On 2/18/21 2:58 PM, Fujii Masao wrote:
>>
>>
>> On 2021/02/17 3:03, Arthur Nascimento wrote:
>>> Hi, Fujii-san,
>>>
>>> On Tue, 16 Feb 2021 at 01:49, Fujii Masao
>>> <masao.fujii@oss.nttdata.com> wrote:
>>>> In the server side, ISTM that CommitTransactionCommand() needs to handle
>>>> the COMMIT AND CHAIN in TBLOCK_SUBCOMMIT case, but it forgot to do that.
>>>> Patch attached. I'm not sure if this is a bug or an intentional
>>>> behavior.
>>>> Probably we need to look at the past discussion about AND CHAIN feature.
>>>
>>> I can confirm that your patch solved it for me. Thanks for looking
>>> into it.
>>
>> Thanks for testing the patch!
>>
>> As far as I read the past discussion about chain transaction,
>> I could not find any mention that current behavior that you reported
>> is intentional.
>>
>> Barring any objection, I will commit the patch that you wrote
>> for psql and the patch I wrote.
>
> No objection from me. According to the standard, a COMMIT should
> destroy all savepoints and terminate the transaction, even if AND CHAIN
> is specified.
You imply that the standard says that COMMIT AND CHAIN should just terminate
the transaction if there are savepoints defined, i.e., should not start new
transaction? Since I can (maybe wrongly) interpret your comment like that,
please let me confirm what the standard says just in case.
I was thinking that COMMIT AND CHAIN should destroy all the savepoints,
terminate the transaction and start new transaction with the same transaction
characteristics immediately.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: BUG #16867: savepoints vs. commit and chain
2021-02-15 20:53 BUG #16867: savepoints vs. commit and chain PG Bug reporting form <noreply@postgresql.org>
2021-02-15 21:47 ` Re: BUG #16867: savepoints vs. commit and chain Arthur Nascimento <tureba@gmail.com>
2021-02-16 04:49 ` Re: BUG #16867: savepoints vs. commit and chain Fujii Masao <masao.fujii@oss.nttdata.com>
2021-02-16 18:03 ` Re: BUG #16867: savepoints vs. commit and chain Arthur Nascimento <tureba@gmail.com>
2021-02-18 13:58 ` Re: BUG #16867: savepoints vs. commit and chain Fujii Masao <masao.fujii@oss.nttdata.com>
2021-02-18 14:10 ` Re: BUG #16867: savepoints vs. commit and chain Vik Fearing <vik@postgresfriends.org>
2021-02-19 04:02 ` Re: BUG #16867: savepoints vs. commit and chain Fujii Masao <masao.fujii@oss.nttdata.com>
@ 2021-02-19 08:29 ` Vik Fearing <vik@postgresfriends.org>
2021-02-19 13:05 ` Re: BUG #16867: savepoints vs. commit and chain Fujii Masao <masao.fujii@oss.nttdata.com>
0 siblings, 1 reply; 9+ messages in thread
From: Vik Fearing @ 2021-02-19 08:29 UTC (permalink / raw)
To: Fujii Masao <masao.fujii@oss.nttdata.com>; Arthur Nascimento <tureba@gmail.com>; +Cc: pgsql-bugs@lists.postgresql.org
On 2/19/21 5:02 AM, Fujii Masao wrote:
>
>
> On 2021/02/18 23:10, Vik Fearing wrote:
>>
>> No objection from me. According to the standard, a COMMIT should
>> destroy all savepoints and terminate the transaction, even if AND CHAIN
>> is specified.
>
> You imply that the standard says that COMMIT AND CHAIN should just
> terminate
> the transaction if there are savepoints defined, i.e., should not start new
> transaction? Since I can (maybe wrongly) interpret your comment like that,
> please let me confirm what the standard says just in case.
The COMMIT terminates the transaction, the AND CHAIN starts a new one.
> I was thinking that COMMIT AND CHAIN should destroy all the savepoints,
> terminate the transaction and start new transaction with the same
> transaction
> characteristics immediately.
Your thinking is correct!
--
Vik Fearing
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: BUG #16867: savepoints vs. commit and chain
2021-02-15 20:53 BUG #16867: savepoints vs. commit and chain PG Bug reporting form <noreply@postgresql.org>
2021-02-15 21:47 ` Re: BUG #16867: savepoints vs. commit and chain Arthur Nascimento <tureba@gmail.com>
2021-02-16 04:49 ` Re: BUG #16867: savepoints vs. commit and chain Fujii Masao <masao.fujii@oss.nttdata.com>
2021-02-16 18:03 ` Re: BUG #16867: savepoints vs. commit and chain Arthur Nascimento <tureba@gmail.com>
2021-02-18 13:58 ` Re: BUG #16867: savepoints vs. commit and chain Fujii Masao <masao.fujii@oss.nttdata.com>
2021-02-18 14:10 ` Re: BUG #16867: savepoints vs. commit and chain Vik Fearing <vik@postgresfriends.org>
2021-02-19 04:02 ` Re: BUG #16867: savepoints vs. commit and chain Fujii Masao <masao.fujii@oss.nttdata.com>
2021-02-19 08:29 ` Re: BUG #16867: savepoints vs. commit and chain Vik Fearing <vik@postgresfriends.org>
@ 2021-02-19 13:05 ` Fujii Masao <masao.fujii@oss.nttdata.com>
0 siblings, 0 replies; 9+ messages in thread
From: Fujii Masao @ 2021-02-19 13:05 UTC (permalink / raw)
To: Vik Fearing <vik@postgresfriends.org>; Arthur Nascimento <tureba@gmail.com>; +Cc: pgsql-bugs@lists.postgresql.org
On 2021/02/19 17:29, Vik Fearing wrote:
> On 2/19/21 5:02 AM, Fujii Masao wrote:
>>
>>
>> On 2021/02/18 23:10, Vik Fearing wrote:
>>>
>>> No objection from me. According to the standard, a COMMIT should
>>> destroy all savepoints and terminate the transaction, even if AND CHAIN
>>> is specified.
>>
>> You imply that the standard says that COMMIT AND CHAIN should just
>> terminate
>> the transaction if there are savepoints defined, i.e., should not start new
>> transaction? Since I can (maybe wrongly) interpret your comment like that,
>> please let me confirm what the standard says just in case.
>
> The COMMIT terminates the transaction, the AND CHAIN starts a new one.
>
>> I was thinking that COMMIT AND CHAIN should destroy all the savepoints,
>> terminate the transaction and start new transaction with the same
>> transaction
>> characteristics immediately.
>
> Your thinking is correct!
Thanks! I pushed the patches.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
^ permalink raw reply [nested|flat] 9+ messages in thread
end of thread, other threads:[~2021-02-19 13:05 UTC | newest]
Thread overview: 9+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2021-02-15 20:53 BUG #16867: savepoints vs. commit and chain PG Bug reporting form <noreply@postgresql.org>
2021-02-15 21:47 ` Arthur Nascimento <tureba@gmail.com>
2021-02-16 04:49 ` Fujii Masao <masao.fujii@oss.nttdata.com>
2021-02-16 18:03 ` Arthur Nascimento <tureba@gmail.com>
2021-02-18 13:58 ` Fujii Masao <masao.fujii@oss.nttdata.com>
2021-02-18 14:10 ` Vik Fearing <vik@postgresfriends.org>
2021-02-19 04:02 ` Fujii Masao <masao.fujii@oss.nttdata.com>
2021-02-19 08:29 ` Vik Fearing <vik@postgresfriends.org>
2021-02-19 13:05 ` Fujii Masao <masao.fujii@oss.nttdata.com>
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