Re: BUG #16667: COMMIT AND CHAIN does not udpates database metrics ie. xact_commit - Mailing list pgsql-bugs

From adam grech
Subject Re: BUG #16667: COMMIT AND CHAIN does not udpates database metrics ie. xact_commit
Date
Msg-id CALbs8FqKWDMwxGfk2A=DD1mBtzH9A-9jAR0VTjMwAe9GWcdW3A@mail.gmail.com
Whole thread Raw
In response to Re: BUG #16667: COMMIT AND CHAIN does not udpates database metrics ie. xact_commit  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
The test case code uses ANSI C and libpq.
I will check does ECPG behaves the same way.

Adam

W dniu pon., 12.10.2020 o 17:21 Tom Lane <tgl@sss.pgh.pa.us> napisał(a):
PG Bug reporting form <noreply@postgresql.org> writes:
> We have an application that uses a new feature COMMIT AND CHAIN, the
> application works generaly OK, but we have noticed that the pg_stat_database
> (xact_commit/xact_rollback) are not updated, as they are if we used
> BEGIN/COMMIT/BEGIN.

I can't reproduce that here.  Indeed, in a quick check I'd say the
opposite: it looks like xact_commit advances twice where I'd only
have expected it to advance once.

                        regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
Next
From: Tom Lane
Date:
Subject: Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering