File Manager

Hackfut Security File Manager

Current Path: /opt/alt/postgresql11/usr/share/man/man7

opt / alt / postgresql11 / usr / share / man / man7 /

📁 ..
📄 ABORT.7(2.2 KB)
📄 ALTER_AGGREGATE.7(3.53 KB)
📄 ALTER_COLLATION.7(2.8 KB)
📄 ALTER_CONVERSION.7(2.9 KB)
📄 ALTER_DATABASE.7(5.28 KB)
📄 ALTER_DEFAULT_PRIVILEGES.7(6.39 KB)
📄 ALTER_DOMAIN.7(6.79 KB)
📄 ALTER_EXTENSION.7(6.54 KB)
📄 ALTER_FOREIGN_DATA_WRAPPER.7(4.37 KB)
📄 ALTER_FOREIGN_TABLE.7(7.6 KB)
📄 ALTER_FUNCTION.7(7.62 KB)
📄 ALTER_GROUP.7(3 KB)
📄 ALTER_INDEX.7(4.51 KB)
📄 ALTER_LANGUAGE.7(2.1 KB)
📄 ALTER_LARGE_OBJECT.7(1.97 KB)
📄 ALTER_OPERATOR.7(3.01 KB)
📄 ALTER_OPERATOR_CLASS.7(2.85 KB)
📄 ALTER_OPERATOR_FAMILY.7(9.09 KB)
📄 ALTER_ROLE.7(8.23 KB)
📄 ALTER_SCHEMA.7(2.31 KB)
📄 ALTER_SEQUENCE.7(7.52 KB)
📄 ALTER_SERVER.7(3.4 KB)
📄 ALTER_TABLE.7(30.51 KB)
📄 ALTER_TABLESPACE.7(3.27 KB)
📄 ALTER_TEXT_SEARCH_CONFIGURATION.7(4.8 KB)
📄 ALTER_TEXT_SEARCH_DICTIONARY.7(4.03 KB)
📄 ALTER_TEXT_SEARCH_PARSER.7(2.27 KB)
📄 ALTER_TEXT_SEARCH_TEMPLATE.7(2.31 KB)
📄 ALTER_TRIGGER.7(2.51 KB)
📄 ALTER_TYPE.7(6.87 KB)
📄 ALTER_USER.7(2.49 KB)
📄 ALTER_USER_MAPPING.7(3.28 KB)
📄 ALTER_VIEW.7(3.89 KB)
📄 ANALYZE.7(7.52 KB)
📄 BEGIN.7(4.08 KB)
📄 CHECKPOINT.7(2.32 KB)
📄 CLOSE.7(2.76 KB)
📄 CLUSTER.7(6.26 KB)
📄 COMMENT.7(9 KB)
📄 COMMIT.7(2.12 KB)
📄 COMMIT_PREPARED.7(2.61 KB)
📄 COPY.7(26.12 KB)
📄 CREATE_AGGREGATE.7(9.44 KB)
📄 CREATE_CAST.7(14.07 KB)
📄 CREATE_COLLATION.7(4.01 KB)
📄 CREATE_CONVERSION.7(3.82 KB)
📄 CREATE_DATABASE.7(7.86 KB)
📄 CREATE_DOMAIN.7(5.37 KB)
📄 CREATE_EXTENSION.7(5.67 KB)
📄 CREATE_FOREIGN_DATA_WRAPPER.7(5.08 KB)
📄 CREATE_FOREIGN_TABLE.7(4.7 KB)
📄 CREATE_FUNCTION.7(21.62 KB)
📄 CREATE_GROUP.7(2.17 KB)
📄 CREATE_INDEX.7(18.72 KB)
📄 CREATE_LANGUAGE.7(9.86 KB)
📄 CREATE_OPERATOR.7(6.92 KB)
📄 CREATE_OPERATOR_CLASS.7(8.54 KB)
📄 CREATE_OPERATOR_FAMILY.7(3.64 KB)
📄 CREATE_ROLE.7(12.18 KB)
📄 CREATE_RULE.7(7.91 KB)
📄 CREATE_SCHEMA.7(5.4 KB)
📄 CREATE_SEQUENCE.7(9.11 KB)
📄 CREATE_SERVER.7(3.68 KB)
📄 CREATE_TABLE.7(39.83 KB)
📄 CREATE_TABLESPACE.7(3.52 KB)
📄 CREATE_TABLE_AS.7(7.94 KB)
📄 CREATE_TEXT_SEARCH_CONFIGURATION.7(3.25 KB)
📄 CREATE_TEXT_SEARCH_DICTIONARY.7(3.39 KB)
📄 CREATE_TEXT_SEARCH_PARSER.7(3.61 KB)
📄 CREATE_TEXT_SEARCH_TEMPLATE.7(3.43 KB)
📄 CREATE_TRIGGER.7(15.11 KB)
📄 CREATE_TYPE.7(28.33 KB)
📄 CREATE_USER.7(2.48 KB)
📄 CREATE_USER_MAPPING.7(3.31 KB)
📄 CREATE_VIEW.7(7.13 KB)
📄 DEALLOCATE.7(2.05 KB)
📄 DECLARE.7(10.26 KB)
📄 DELETE.7(7.39 KB)
📄 DISCARD.7(2.53 KB)
📄 DO.7(3.13 KB)
📄 DROP_AGGREGATE.7(2.58 KB)
📄 DROP_CAST.7(2.29 KB)
📄 DROP_COLLATION.7(2.34 KB)
📄 DROP_CONVERSION.7(2.4 KB)
📄 DROP_DATABASE.7(2.41 KB)
📄 DROP_DOMAIN.7(2.25 KB)
📄 DROP_EXTENSION.7(2.64 KB)
📄 DROP_FOREIGN_DATA_WRAPPER.7(2.52 KB)
📄 DROP_FOREIGN_TABLE.7(2.5 KB)
📄 DROP_FUNCTION.7(3.27 KB)
📄 DROP_GROUP.7(1.6 KB)
📄 DROP_INDEX.7(2.99 KB)
📄 DROP_LANGUAGE.7(2.77 KB)
📄 DROP_OPERATOR.7(2.9 KB)
📄 DROP_OPERATOR_CLASS.7(3.38 KB)
📄 DROP_OPERATOR_FAMILY.7(3.16 KB)
📄 DROP_OWNED.7(3.02 KB)
📄 DROP_ROLE.7(3.08 KB)
📄 DROP_RULE.7(2.2 KB)
📄 DROP_SCHEMA.7(2.55 KB)
📄 DROP_SEQUENCE.7(2.38 KB)
📄 DROP_SERVER.7(2.3 KB)
📄 DROP_TABLE.7(2.88 KB)
📄 DROP_TABLESPACE.7(2.51 KB)
📄 DROP_TEXT_SEARCH_CONFIGURATION.7(2.76 KB)
📄 DROP_TEXT_SEARCH_DICTIONARY.7(2.67 KB)
📄 DROP_TEXT_SEARCH_PARSER.7(2.58 KB)
📄 DROP_TEXT_SEARCH_TEMPLATE.7(2.61 KB)
📄 DROP_TRIGGER.7(2.52 KB)
📄 DROP_TYPE.7(2.43 KB)
📄 DROP_USER.7(1.68 KB)
📄 DROP_USER_MAPPING.7(2.59 KB)
📄 DROP_VIEW.7(2.34 KB)
📄 END.7(2.21 KB)
📄 EXECUTE.7(2.96 KB)
📄 EXPLAIN.7(12.89 KB)
📄 FETCH.7(8.52 KB)
📄 GRANT.7(21.41 KB)
📄 INSERT.7(8.74 KB)
📄 LISTEN.7(3.53 KB)
📄 LOAD.7(2.58 KB)
📄 LOCK.7(7.92 KB)
📄 MOVE.7(2.96 KB)
📄 NOTIFY.7(7.96 KB)
📄 PREPARE.7(6.2 KB)
📄 PREPARE_TRANSACTION.7(5.77 KB)
📄 REASSIGN_OWNED.7(3.08 KB)
📄 REINDEX.7(7.85 KB)
📄 RELEASE_SAVEPOINT.7(3.06 KB)
📄 RESET.7(2.96 KB)
📄 REVOKE.7(10.46 KB)
📄 ROLLBACK.7(2.12 KB)
📄 ROLLBACK_PREPARED.7(2.64 KB)
📄 ROLLBACK_TO_SAVEPOINT.7(4.01 KB)
📄 SAVEPOINT.7(3.55 KB)
📄 SECURITY_LABEL.7(5.29 KB)
📄 SELECT.7(52.77 KB)
📄 SELECT_INTO.7(4.53 KB)
📄 SET.7(7.46 KB)
📄 SET_CONSTRAINTS.7(4.56 KB)
📄 SET_ROLE.7(4.38 KB)
📄 SET_SESSION_AUTHORIZATION.7(3.92 KB)
📄 SET_TRANSACTION.7(8.44 KB)
📄 SHOW.7(4.25 KB)
📄 START_TRANSACTION.7(2.93 KB)
📄 TABLE.7(18 B)
📄 TRUNCATE.7(6.24 KB)
📄 UNLISTEN.7(2.77 KB)
📄 UPDATE.7(10.63 KB)
📄 VACUUM.7(7.09 KB)
📄 VALUES.7(6.97 KB)
📄 WITH.7(18 B)

Editing: PREPARE.7

'\" t
.\"     Title: PREPARE
.\"    Author: The PostgreSQL Global Development Group
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
.\"      Date: 2017-11-06
.\"    Manual: PostgreSQL 9.2.24 Documentation
.\"    Source: PostgreSQL 9.2.24
.\"  Language: English
.\"
.TH "PREPARE" "7" "2017-11-06" "PostgreSQL 9.2.24" "PostgreSQL 9.2.24 Documentation"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.\" http://bugs.debian.org/507673
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
PREPARE \- prepare a statement for execution
.\" PREPARE
.\" prepared statements: creating
.SH "SYNOPSIS"
.sp
.nf
PREPARE \fIname\fR [ ( \fIdata_type\fR [, \&.\&.\&.] ) ] AS \fIstatement\fR
.fi
.SH "DESCRIPTION"
.PP
\fBPREPARE\fR
creates a prepared statement\&. A prepared statement is a server\-side object that can be used to optimize performance\&. When the
\fBPREPARE\fR
statement is executed, the specified statement is parsed, analyzed, and rewritten\&. When an
\fBEXECUTE\fR
command is subsequently issued, the prepared statement is planned and executed\&. This division of labor avoids repetitive parse analysis work, while allowing the execution plan to depend on the specific parameter values supplied\&.
.PP
Prepared statements can take parameters: values that are substituted into the statement when it is executed\&. When creating the prepared statement, refer to parameters by position, using
$1,
$2, etc\&. A corresponding list of parameter data types can optionally be specified\&. When a parameter\*(Aqs data type is not specified or is declared as
unknown, the type is inferred from the context in which the parameter is used (if possible)\&. When executing the statement, specify the actual values for these parameters in the
\fBEXECUTE\fR
statement\&. Refer to
\fBEXECUTE\fR(7)
for more information about that\&.
.PP
Prepared statements only last for the duration of the current database session\&. When the session ends, the prepared statement is forgotten, so it must be recreated before being used again\&. This also means that a single prepared statement cannot be used by multiple simultaneous database clients; however, each client can create their own prepared statement to use\&. Prepared statements can be manually cleaned up using the
\fBDEALLOCATE\fR(7)
command\&.
.PP
Prepared statements have the largest performance advantage when a single session is being used to execute a large number of similar statements\&. The performance difference will be particularly significant if the statements are complex to plan or rewrite, for example, if the query involves a join of many tables or requires the application of several rules\&. If the statement is relatively simple to plan and rewrite but relatively expensive to execute, the performance advantage of prepared statements will be less noticeable\&.
.SH "PARAMETERS"
.PP
\fIname\fR
.RS 4
An arbitrary name given to this particular prepared statement\&. It must be unique within a single session and is subsequently used to execute or deallocate a previously prepared statement\&.
.RE
.PP
\fIdata_type\fR
.RS 4
The data type of a parameter to the prepared statement\&. If the data type of a particular parameter is unspecified or is specified as
unknown, it will be inferred from the context in which the parameter is used\&. To refer to the parameters in the prepared statement itself, use
$1,
$2, etc\&.
.RE
.PP
\fIstatement\fR
.RS 4
Any
\fBSELECT\fR,
\fBINSERT\fR,
\fBUPDATE\fR,
\fBDELETE\fR, or
\fBVALUES\fR
statement\&.
.RE
.SH "NOTES"
.PP
If a prepared statement is executed enough times, the server may eventually decide to save and re\-use a generic plan rather than re\-planning each time\&. This will occur immediately if the prepared statement has no parameters; otherwise it occurs only if the generic plan appears to be not much more expensive than a plan that depends on specific parameter values\&. Typically, a generic plan will be selected only if the query\*(Aqs performance is estimated to be fairly insensitive to the specific parameter values supplied\&.
.PP
To examine the query plan
PostgreSQL
is using for a prepared statement, use
\fBEXPLAIN\fR(7)\&. If a generic plan is in use, it will contain parameter symbols
$\fIn\fR, while a custom plan will have the current actual parameter values substituted into it\&.
.PP
For more information on query planning and the statistics collected by
PostgreSQL
for that purpose, see the
\fBANALYZE\fR(7)
documentation\&.
.PP
You can see all prepared statements available in the session by querying the
pg_prepared_statements
system view\&.
.SH "EXAMPLES"
.PP
Create a prepared statement for an
\fBINSERT\fR
statement, and then execute it:
.sp
.if n \{\
.RS 4
.\}
.nf
PREPARE fooplan (int, text, bool, numeric) AS
    INSERT INTO foo VALUES($1, $2, $3, $4);
EXECUTE fooplan(1, \*(AqHunter Valley\*(Aq, \*(Aqt\*(Aq, 200\&.00);
.fi
.if n \{\
.RE
.\}
.PP
Create a prepared statement for a
\fBSELECT\fR
statement, and then execute it:
.sp
.if n \{\
.RS 4
.\}
.nf
PREPARE usrrptplan (int) AS
    SELECT * FROM users u, logs l WHERE u\&.usrid=$1 AND u\&.usrid=l\&.usrid
    AND l\&.date = $2;
EXECUTE usrrptplan(1, current_date);
.fi
.if n \{\
.RE
.\}
.sp
Note that the data type of the second parameter is not specified, so it is inferred from the context in which
$2
is used\&.
.SH "COMPATIBILITY"
.PP
The SQL standard includes a
\fBPREPARE\fR
statement, but it is only for use in embedded SQL\&. This version of the
\fBPREPARE\fR
statement also uses a somewhat different syntax\&.
.SH "SEE ALSO"
\fBDEALLOCATE\fR(7), \fBEXECUTE\fR(7)

Hackfut Security File Manager

Editing: PREPARE.7

Upload File

Create Folder