pg_prepared_statements

From: rob stone <floriparob(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: pg_prepared_statements
Date: 2020-01-21 03:00:28
Message-ID: 2fb481e6017498dd084876bb98f106da575eb604.camel@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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.

TIA,
Robert

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2020-01-21 03:18:02 Re: pg_prepared_statements
Previous Message Ron 2020-01-20 16:41:51 Re: postgresql commands(psql,createdb,dropdb) are not working from shell script