PostgreSQL 7.4.7 Documentation
PrevFast BackwardFast ForwardNext

PREPARE

Name

PREPARE -- prepare a statement for execution

Synopsis

PREPARE plan_name [ (datatype [, ...] ) ] AS statement

Description

PREPARE creates a prepared statement. A prepared statement is a server-side object that can be used to optimize performance. When the PREPARE statement is executed, the specified statement is parsed, rewritten, and planned. When an EXECUTE command is subsequently issued, the prepared statement need only be executed. Thus, the parsing, rewriting, and planning stages are only performed once, instead of every time the statement is executed.

Prepared statements can take parameters: values that are substituted into the statement when it is executed. To include parameters in a prepared statement, supply a list of data types in the PREPARE statement, and,H="100%"IV CLASS="REFSECT1" >

See Also

VACUUM
PrevHomeNext
psqlUpPostgreSQL Server Applications
./usr/share/doc/postgresql-doc/html/release-7-1.html0000644000000000000000000003136410177403072022363 0ustar rootroot00000000000000 Release 7.1
PostgreSQL 7.4.7 Documentation
PrevFast BackwardAppendix E. Release NotesFast ForwardNext

E.30. Release 7.1

Release date: 2001-04-13

This release focuses on removing limitations that have existed in the PostgreSQL code for many years.

Major changes in this release:

Write-ahead Log (WAL)

To maintain database consistency in case of an operating system crash, previous releases of PostgreSQL have forced all data modifications to disk before each transaction commit. With WAL, only one log file must be flushed to disk, greatly improving performance. If you have been using -F in previous releases to disable disk flushes, you may want to consider discontinuing its use.

TOAST

TOAST - Previous releases had a compiled-in row length limit, typically 8k - 32k. This limit made storage of long text fields difficult. With TOAST, long rows of any length can be stored with good performance.

Outer Joins

We now support outer joins. The UNION/NOT IN workaround for outer joins is no l