| From: | adam grech <axgrech(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16667: COMMIT AND CHAIN does not udpates database metrics ie. xact_commit |
| Date: | 2020-10-12 21:23:30 |
| Message-ID: | CALbs8FqKWDMwxGfk2A=DD1mBtzH9A-9jAR0VTjMwAe9GWcdW3A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)sss(dot)pgh(dot)pa(dot)us> napisał(a):
> PG Bug reporting form <noreply(at)postgresql(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-10-12 22:16:52 | Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering |
| Previous Message | Tom Lane | 2020-10-12 20:03:10 | Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering |