Re: Postgres prepare statement caching issue in postgres command line

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Soumya Prasad Ukil <soumyo_ju(at)yahoo(dot)co(dot)in>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Postgres prepare statement caching issue in postgres command line
Date: 2021-05-22 22:23:48
Message-ID: f0a49017-164e-7ff7-edf8-ebdc35830ab7@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 5/22/21 1:25 PM, Soumya Prasad Ukil wrote:
> I have been using postgres prepare statement feature through JDBC. I
> could see the same prepare statement multiple times, parsing is not
> happening in postgres backend, which is expected. However I do the same
> in psql command line, that does not happen. It goes to parsing every
> time I execute
>
> Using the following query:
>
> postgres=> PREPARE parallel_execute1(text, text) AS insert into actor
> (first_name, last_name) values ($1, $2);
> postgres=> PREPARE parallel_execute2(int, int) AS insert into film_actor
> (actor_id, film_id) values($1, $2);
> postgres=> execute parallel_execute1;
> postgres=> execute parallel_execute2;

Where are the arguments for the parameters?

>
>
> I have executed both prepared statements 10 times. I could see every
> time both queries went through parsing. How do I make sure that they do
> not need parsing in command line? JDBC it works in expected manner. Same
> code does not go for parsing each time. How can I have same behaviour in
> pgsql command line?
>

How are you determining the above?

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bryn Llewellyn 2021-05-23 00:54:07 Re: The contents of the pg_timezone_names view bring some surprises
Previous Message Ron 2021-05-22 22:11:21 Re: Postgres prepare statement caching issue in postgres command line