Horton

Re: Query Jumbling for CALL and SET utility statements

Sami Imseih <simseih@amazon.com>

View thread View on postgr.es
From: "Imseih (AWS), Sami" <simseih@amazon.com>
To: "Drouvot, Bertrand" <bdrouvot@amazon.fr>, Julien Rouhaud <rjuju123@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, "Schneider (AWS), Jeremy" <schnjere@amazon.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Pavel Stehule <pavel.stehule@gmail.com>, Andres Freund <andres@anarazel.de>
Date: 2022-09-14T13:20:09Z
Lists: pgsql-hackers 
> Attached v5 to normalize 2PC commands too, so that we get things like:
A nit on the documentation for v5, otherwise lgtm.

Plannable queries (that is, SELECT, INSERT, UPDATE, and DELETE) as well as CALL, SET
and two-phase commit commands PREPARE TRANSACTION, , COMMIT PREPARED
and ROLLBACK PREPARED are combined

---- to ----

Plannable queries (that is, SELECT, INSERT, UPDATE, and DELETE) as well as CALL,
SET, PREPARE TRANSACTION, COMMIT PREPARED and ROLLBACK PREPARED are combined


---

Regards,

Sami Imseih
Amazon Web Services (AWS)

Commits

  1. Show values of SET statements as constants in pg_stat_statements

  2. Teach contrib/pg_stat_statements to handle multi-statement commands better.