linkend="sql-createfunction"
- endterm="sql-createfunction-title">. Disabling validation is
- occasionally useful to avoid problems such as forward
- references when restoring function definitions from a dump.
+ endterm="sql-createfunction-title">. Disabling validation is
+ occasionally useful to avoid problems such as forward references
+ when restoring function definitions from a dump.
A read-only SQL transaction cannot alter non-temporary tables.
This parameter controls the default read-only status of each new
- transaction. The default is off (read/write).
+ transaction. The default is off> (read/write).
CST, EST, and
SAT are interpreted as Australian time
zones rather than as North/South American time zones and
- Saturday. The default is off.
+ Saturday. The default is off>.
Determines whether EXPLAIN VERBOSE> uses the
indented or non-indented format for displaying detailed
- query-tree dumps. The default is on.
+ query-tree dumps. The default is on>.
- When on>, tables that are referenced by a query
- will be automatically added to the FROM> clause if
- not already present. This behavior does not comply with the
- SQL standard and many people dislike it because it can mask
- mistakes (such as referencing a table where you should have
- referenced its alias). The default is off>. This
- variable can be enabled for compatibility with releases of
-
PostgreSQL> prior to 8.1, where this behavior
- was allowed by default.
+ When on, tables that are referenced by a query will be
+ automatically added to the FROM> clause if not
+ already present. This behavior does not comply with the SQL
+ standard and many people dislike it because it can mask mistakes
+ (such as referencing a table where you should have referenced
+ its alias). The default is off>. This variable can be
+ enabled for compatibility with releases of
+
PostgreSQL> prior to 8.1, where this behavior was
+ allowed by default.
This controls the inheritance semantics, in particular whether
subtables are included by various commands by default. They were
not included in versions prior to 7.1. If you need the old
- behavior you can set this variable to off, but in the long run
- you are encouraged to change your applications to use the
- ONLY key word to exclude subtables. See
- for more information about inheritance.
+ behavior you can set this variable to off>, but in
+ the long run you are encouraged to change your applications to
+ use the ONLY key word to exclude subtables.
+ See for more information about
+ inheritance.
- When on>, a warning is issued if a backslash
- (\>) appears in an ordinary string literal
- ('...'> syntax). The default is off>.
+ When on, a warning is issued if a backslash (\>)
+ appears in an ordinary string literal ('...'>
+ syntax). The default is off>.
Escape string syntax (E'...'>) should be used for
- When turned on, expressions of the form
- expr> = NULL (or NULL
- = expr>) are treated as
+ When on, expressions of the form expr> =
+ NULL (or NULL =
+ expr>) are treated as
expr> IS NULL, that is, they
return true if expr> evaluates to the null value,
and false otherwise. The correct SQL-spec-compliant behavior of
expr> = NULL is to always
- return null (unknown). Therefore this option defaults to off.
+ return null (unknown). Therefore this option defaults to
+ off>.
must be defined when
PostgreSQL is
built (accomplished by the configure option
). Note that
- debug_assertions defaults to on if
-
PostgreSQL has been built with
+ debug_assertions defaults to on>
+
if PostgreSQL has been built with
assertions enabled.
corruption has occurred due to hardware or software error. You should
generally not set this on until you have given up hope of recovering
data from the damaged page(s) of a table. The
- default setting is off, and it can only be changed by a superuser.
+ default setting is off>, and it can only be changed
+ by a superuser.