Re: Query Jumbling for CALL and SET utility statements - Mailing list pgsql-hackers

From Imseih (AWS), Sami
Subject Re: Query Jumbling for CALL and SET utility statements
Date
Msg-id 2E1E3551-5E07-4DBB-90F7-64E0C8AEDD34@amazon.com
Whole thread Raw
In response to Re: Query Jumbling for CALL and SET utility statements  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List 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)



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [PoC] Let libpq reject unexpected authentication requests
Next
From: Tom Lane
Date:
Subject: clang 15 doesn't like our JIT code