Hi Justin,
Thanks for your response.
I suspect JDBC is using parameterized queries (postgres $1, $2, ..) and psql
isn't (unless you type "prepare p AS SELECT ..." and execute p(.., .., ..)"
isn't (unless you type "prepare p AS SELECT ..." and execute p(.., .., ..)"
Yes JDBC is using parameterized queries which get constructed dynamically depending upon user privileges in the application.Does this cause any issues?
I don't know what server version you have, so I don't know whether to suggest
testing with plan_cache_mode=force_custom_plan
testing with plan_cache_mode=force_custom_plan
It's Postgres 11.5.
I will look into links you shared.
Regards,
AD.
On Fri, Dec 4, 2020 at 1:47 PM Justin Pryzby <pryzby@xxxxxxxxxxxxx> wrote:
On Fri, Dec 04, 2020 at 01:31:14PM +0530, aditya desai wrote:
> Hi Justin,
> Many thanks for your response. Please see my response below.
>
> What do you mean by API ? If it's a different client, how does it connect ?
> Queries are getting called from Web UI built in Microservices spring boot.
> It connected to Database with JDBC driver. Developers have handled
> connection pooling at the Application side.
>
> What db driver ?
>
> Driver is JDBC
I suspect JDBC is using parameterized queries (postgres $1, $2, ..) and psql
isn't (unless you type "prepare p AS SELECT ..." and execute p(.., .., ..)"
You can search and find other people who reported similar issues.
https://www.postgresql.org/message-id/flat/A737B7A37273E048B164557ADEF4A58B50FB8D5E%40ntex2010i.host.magwien.gv.at
https://www.postgresql.org/message-id/flat/20200504191201.GU28974%40telsasoft.com
I don't know what server version you have, so I don't know whether to suggest
testing with plan_cache_mode=force_custom_plan
--
Justin
