On 5/23/21 12:04 AM, Soumya Prasad Ukil wrote:
postgres=> execute parallel_execute1('a', 'b');
postgres=> execute parallel_execute2(1, 2);
I have enabled pg_stats_statement chrome extension. I have enabled
postgres log inside post_parse_analyze_hook
and also debugging through gdb using break
postgres=> execute parallel_execute1('a', 'b');postgres=> execute
parallel_execute2(1, 2);
I have enabled pg_stats_statement chrome extension. I have enabled postgres log
inside post_parse_analyze_hook and also debugging through gdb using break
point. I see it is always going through parse call
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 happ
On 5/22/21 4:11 PM, Tom Lane wrote:
Soumya Prasad Ukil writes:
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,
Soumya Prasad Ukil writes:
> 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
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
Usi
