| From: | "Imseih (AWS), Sami" <simseih(at)amazon(dot)com> |
|---|---|
| To: | "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)fr>, Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, "Schneider (AWS), Jeremy" <schnjere(at)amazon(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: Query Jumbling for CALL and SET utility statements |
| Date: | 2022-09-14 13:20:09 |
| Message-ID: | 7B7BB4D2-9FF8-4F91-8880-1E52655B2D3E@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2022-09-14 13:56:43 | Re: Avoid redudant initialization and possible memory leak (src/backend/parser/parse_relation.c) |
| Previous Message | kuroda.hayato@fujitsu.com | 2022-09-14 12:26:52 | RE: logical replication restrictions |