| PostgreSQL 8.3.3 Documentation | ||||
|---|---|---|---|---|
| Prev | Fast Backward | Chapter 44. System Catalogs | Fast Forward | Next |
The pg_prepared_statements view displays all the prepared statements that are available in the current session. See PREPARE for more information about prepared statements.
pg_prepared_statements contains one row for each prepared statement. Rows are added to the view when a new prepared statement is created and removed when a prepared statement is released (for example, via the DEALLOCATE command).
Table 44-47. pg_prepared_statements Columns
| Name | Type | Description |
|---|---|---|
| name | text | The identifier of the prepared statement |
| statement | text | The query string submitted by the client to create this prepared statement. For prepared statements created via SQL, this is the PREPARE statement submitted by the client. For prepared statements created via the frontend/backend protocol, this is the text of the prepared statement itself |
| prepare_time | timestamptz | The time at which the prepared statement was created |
| parameter_types | regtype[] | The expected parameter types for the prepared statement in the form of an array of regtype. The OID corresponding to an element of this array can be obtained by casting the regtype value to oid |
| from_sql | boolean | true if the prepared statement was created via the PREPARE SQL statement; false if the statement was prepared via the frontend/backend protocol |
The pg_prepared_statements view is read only.
No comments could be found for this page.
Please use this form to add your own comments regarding your experience with particular features of PostgreSQL, clarifications of the documentation, or hints for other users. Please note, this is not a support forum, and your IP address will be logged. If you have a question or need help, please see the faq, try a mailing list, or join us on IRC. Note that submissions containing URLs or other keywords commonly found in 'spam' comments may be silently discarded. Please contact the webmaster if you think this is happening to you in error.
In order to submit a comment, you must have a community account.
* denotes required field