Search Postgresql Archives

Re: pg_prepared_statements

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jan 20, 2020 at 8:00 PM rob stone <floriparob@xxxxxxxxx> wrote:
Hello,

PostgreSQL 11.6 (Debian 11.6-2~sid1) on x86_64-pc-linux-gnu, compiled
by gcc (Debian 9.2.1-21) 9.2.1 20191130, 64-bit

Is there something awry with the pg_prepared_statements view?
This is the only row found and it is NOT created by the application.

name    statement       prepare_time            parameter_types from_sql
S_1     ROLLBACK        2020-01-21 12:35:35.031257      {}      false


In the development environment every statement is logged, however for
some reason the DEALLOCATE's never appear in the logs. This could be
caused by the view not recording the prepared statement, as the
DEALLOCATE is only made if the prepared statement name exists in the
view.

max_prepared_transactions = 6 is the value set in postgresql.conf.

I don't know why that particular record exists but your comment about the application not creating it and DEALLOCATE's never appearing in the log suggests to me a misunderstanding of what this view shows.


Specifically it is not a "log" in the transaction sense and its only shows current session data.

David J.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux