From: | legrand legrand <legrand_legrand(at)hotmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | RE: pg_stat_statements doesn't track commit from pl/pgsql blocks |
Date: | 2019-02-22 20:47:22 |
Message-ID: | DB6PR0301MB213527DA4E3EFDA404EB4418907F0@DB6PR0301MB2135.eurprd03.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
forgot to cc pgsql-general list
________________________________
De : legrand legrand <legrand_legrand(at)hotmail(dot)com>
Envoyé : vendredi 22 février 2019 20:26
À : Bruce Momjian
Objet : RE: pg_stat_statements doesn't track commit from pl/pgsql blocks
Hello Bruce,
thank you for taking time to answer.
yes, I was expecting something like
SELECT calls,query FROM pg_stat_statements;
calls | query
-------+-----------------------------------
1 | select pg_stat_statements_reset()
1 | do $$ begin commit; end $$
1 | commit
as I didn't found any other place to track this 'commit' information.
nb: I don't "want" anything this is just an open question,
and I'm perfectly able to ear that its not expected or not easy to implement.
Regards
PAscal
From | Date | Subject | |
---|---|---|---|
Next Message | Tiffany Thang | 2019-02-22 21:00:43 | Re: Copy entire schema A to a different schema B |
Previous Message | Sergey Burladyan | 2019-02-22 19:14:32 | Re: Running from 9.6 backups sometimes fails with fatal error |