| From: | "Imseih (AWS), Sami" <simseih(at)amazon(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, "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-16 15:08:59 |
| Message-ID: | 2E1E3551-5E07-4DBB-90F7-64E0C8AEDD34@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> The utility commands for cursor like DECLARE CURSOR seem to have the same issue
> and can cause lots of pgss entries. For example, when we use postgres_fdw and
> execute "SELECT * FROM <foreign table> WHERE id = 10" five times in the same
> transaction, the following commands are executed in the remote PostgreSQL server
> and recorded as pgss entries there.
> DECLARE c1 CURSOR FOR ...
> DECLARE c2 CURSOR FOR ...
> DECLARE c3 CURSOR FOR ...
+1
I also made this observation recently and have a patch to suggest
to improve tis situation. I will start a separate thread for this.
Regards,
--
Sami Imseih
Amazon Web Services (AWS)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-09-16 15:40:46 | clang 15 doesn't like our JIT code |
| Previous Message | Peter Eisentraut | 2022-09-16 14:56:20 | Re: [PoC] Let libpq reject unexpected authentication requests |