|
Server : Apache/2.2.2 (Fedora) System : Linux App1.pathumtani.go.th 2.6.20-1.2320.fc5smp #1 SMP Tue Jun 12 19:40:16 EDT 2007 i686 User : apache ( 48) PHP Version : 5.2.9 Disable Function : NONE Directory : /proc/self/root/usr/share/doc/postgresql-8.1.9/html/ |
Upload File : |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Client Connection Defaults</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REV="MADE"
HREF="mailto:pgsql-docs@postgresql.org"><LINK
REL="HOME"
TITLE="PostgreSQL 8.1.9 Documentation"
HREF="index.html"><LINK
REL="UP"
TITLE="Server Configuration"
HREF="runtime-config.html"><LINK
REL="PREVIOUS"
TITLE="Automatic Vacuuming"
HREF="runtime-config-autovacuum.html"><LINK
REL="NEXT"
TITLE="Lock Management"
HREF="runtime-config-locks.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="stylesheet.css"><META
HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=ISO-8859-1"><META
NAME="creation"
CONTENT="2007-04-20T04:40:08"></HEAD
><BODY
CLASS="SECT1"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="5"
ALIGN="center"
VALIGN="bottom"
>PostgreSQL 8.1.9 Documentation</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
HREF="runtime-config-autovacuum.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
HREF="runtime-config.html"
>Fast Backward</A
></TD
><TD
WIDTH="60%"
ALIGN="center"
VALIGN="bottom"
>Chapter 17. Server Configuration</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="top"
><A
HREF="runtime-config.html"
>Fast Forward</A
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="top"
><A
HREF="runtime-config-locks.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="RUNTIME-CONFIG-CLIENT"
>17.10. Client Connection Defaults</A
></H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="RUNTIME-CONFIG-CLIENT-STATEMENT"
>17.10.1. Statement Behavior</A
></H2
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="GUC-SEARCH-PATH"
></A
><TT
CLASS="VARNAME"
>search_path</TT
> (<TT
CLASS="TYPE"
>string</TT
>)</DT
><DD
><P
> This variable specifies the order in which schemas are searched
when an object (table, data type, function, etc.) is referenced by a
simple name with no schema component. When there are objects of
identical names in different schemas, the one found first
in the search path is used. An object that is not in any of the
schemas in the search path can only be referenced by specifying
its containing schema with a qualified (dotted) name.
</P
><P
> The value for <TT
CLASS="VARNAME"
>search_path</TT
> has to be a comma-separated
list of schema names. If one of the list items is
the special value <TT
CLASS="LITERAL"
>$user</TT
>, then the schema
having the name returned by <CODE
CLASS="FUNCTION"
>SESSION_USER</CODE
> is substituted, if there
is such a schema. (If not, <TT
CLASS="LITERAL"
>$user</TT
> is ignored.)
</P
><P
> The system catalog schema, <TT
CLASS="LITERAL"
>pg_catalog</TT
>, is always
searched, whether it is mentioned in the path or not. If it is
mentioned in the path then it will be searched in the specified
order. If <TT
CLASS="LITERAL"
>pg_catalog</TT
> is not in the path then it will
be searched <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>before</I
></SPAN
> searching any of the path items.
</P
><P
> Likewise, the current session's temporary-table schema,
<TT
CLASS="LITERAL"
>pg_temp_<TT
CLASS="REPLACEABLE"
><I
>nnn</I
></TT
></TT
>, is always searched if it
exists. It can be explicitly listed in the path by using the
alias <TT
CLASS="LITERAL"
>pg_temp</TT
>. If it is not listed in the path then
it is searched first (before even <TT
CLASS="LITERAL"
>pg_catalog</TT
>). However,
the temporary schema is only searched for relation (table, view,
sequence, etc) and data type names. It will never be searched for
function or operator names.
</P
><P
> When objects are created without specifying a particular target
schema, they will be placed in the first schema listed
in the search path. An error is reported if the search path is
empty.
</P
><P
> The default value for this parameter is
<TT
CLASS="LITERAL"
>'$user, public'</TT
> (where the second part will be
ignored if there is no schema named <TT
CLASS="LITERAL"
>public</TT
>).
This supports shared use of a database (where no users
have private schemas, and all share use of <TT
CLASS="LITERAL"
>public</TT
>),
private per-user schemas, and combinations of these. Other
effects can be obtained by altering the default search path
setting, either globally or per-user.
</P
><P
> The current effective value of the search path can be examined
via the <ACRONYM
CLASS="ACRONYM"
>SQL</ACRONYM
> function
<CODE
CLASS="FUNCTION"
>current_schemas()</CODE
>. This is not quite the same as
examining the value of <TT
CLASS="VARNAME"
>search_path</TT
>, since
<CODE
CLASS="FUNCTION"
>current_schemas()</CODE
> shows how the requests
appearing in <TT
CLASS="VARNAME"
>search_path</TT
> were resolved.
</P
><P
> For more information on schema handling, see <A
HREF="ddl-schemas.html"
>Section 5.7</A
>.
</P
></DD
><DT
><A
NAME="GUC-DEFAULT-TABLESPACE"
></A
><TT
CLASS="VARNAME"
>default_tablespace</TT
> (<TT
CLASS="TYPE"
>string</TT
>)</DT
><DD
><P
> This variable specifies the default tablespace in which to create
objects (tables and indexes) when a <TT
CLASS="COMMAND"
>CREATE</TT
> command does
not explicitly specify a tablespace.
</P
><P
> The value is either the name of a tablespace, or an empty string
to specify using the default tablespace of the current database.
If the value does not match the name of any existing tablespace,
<SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> will automatically use the default
tablespace of the current database.
</P
><P
> For more information on tablespaces,
see <A
HREF="manage-ag-tablespaces.html"
>Section 19.6</A
>.
</P
></DD
><DT
><A
NAME="GUC-CHECK-FUNCTION-BODIES"
></A
><TT
CLASS="VARNAME"
>check_function_bodies</TT
> (<TT
CLASS="TYPE"
>boolean</TT
>)</DT
><DD
><P
> This parameter is normally on. When set to <TT
CLASS="LITERAL"
>off</TT
>, it
disables validation of the function body string during <A
HREF="sql-createfunction.html"
><I
>CREATE FUNCTION</I
></A
>. Disabling validation is
occasionally useful to avoid problems such as forward references
when restoring function definitions from a dump.
</P
></DD
><DT
><A
NAME="GUC-DEFAULT-TRANSACTION-ISOLATION"
></A
><TT
CLASS="VARNAME"
>default_transaction_isolation</TT
> (<TT
CLASS="TYPE"
>string</TT
>)</DT
><DD
><P
> Each SQL transaction has an isolation level, which can be
either <SPAN
CLASS="QUOTE"
>"read uncommitted"</SPAN
>, <SPAN
CLASS="QUOTE"
>"read
committed"</SPAN
>, <SPAN
CLASS="QUOTE"
>"repeatable read"</SPAN
>, or
<SPAN
CLASS="QUOTE"
>"serializable"</SPAN
>. This parameter controls the
default isolation level of each new transaction. The default
is <SPAN
CLASS="QUOTE"
>"read committed"</SPAN
>.
</P
><P
> Consult <A
HREF="mvcc.html"
>Chapter 12</A
> and <A
HREF="sql-set-transaction.html"
><I
>SET TRANSACTION</I
></A
> for more information.
</P
></DD
><DT
><A
NAME="GUC-DEFAULT-TRANSACTION-READ-ONLY"
></A
><TT
CLASS="VARNAME"
>default_transaction_read_only</TT
> (<TT
CLASS="TYPE"
>boolean</TT
>)</DT
><DD
><P
> 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 <TT
CLASS="LITERAL"
>off</TT
> (read/write).
</P
><P
> Consult <A
HREF="sql-set-transaction.html"
><I
>SET TRANSACTION</I
></A
> for more information.
</P
></DD
><DT
><A
NAME="GUC-STATEMENT-TIMEOUT"
></A
><TT
CLASS="VARNAME"
>statement_timeout</TT
> (<TT
CLASS="TYPE"
>integer</TT
>)</DT
><DD
><P
> Abort any statement that takes over the specified number of
milliseconds. If <TT
CLASS="VARNAME"
>log_min_error_statement</TT
> is set to
<TT
CLASS="LITERAL"
>ERROR</TT
> or lower, the statement that timed out will also be
logged. A value of zero (the default) turns off the
limitation.
</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="RUNTIME-CONFIG-CLIENT-FORMAT"
>17.10.2. Locale and Formatting</A
></H2
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="GUC-DATESTYLE"
></A
><TT
CLASS="VARNAME"
>DateStyle</TT
> (<TT
CLASS="TYPE"
>string</TT
>)</DT
><DD
><P
> Sets the display format for date and time values, as well as the
rules for interpreting ambiguous date input values. For
historical reasons, this variable contains two independent
components: the output format specification (<TT
CLASS="LITERAL"
>ISO</TT
>,
<TT
CLASS="LITERAL"
>Postgres</TT
>, <TT
CLASS="LITERAL"
>SQL</TT
>, or <TT
CLASS="LITERAL"
>German</TT
>)
and the input/output specification for year/month/day ordering
(<TT
CLASS="LITERAL"
>DMY</TT
>, <TT
CLASS="LITERAL"
>MDY</TT
>, or <TT
CLASS="LITERAL"
>YMD</TT
>). These
can be set separately or together. The keywords <TT
CLASS="LITERAL"
>Euro</TT
>
and <TT
CLASS="LITERAL"
>European</TT
> are synonyms for <TT
CLASS="LITERAL"
>DMY</TT
>; the
keywords <TT
CLASS="LITERAL"
>US</TT
>, <TT
CLASS="LITERAL"
>NonEuro</TT
>, and
<TT
CLASS="LITERAL"
>NonEuropean</TT
> are synonyms for <TT
CLASS="LITERAL"
>MDY</TT
>. See
<A
HREF="datatype-datetime.html"
>Section 8.5</A
> for more information. The
default is <TT
CLASS="LITERAL"
>ISO, MDY</TT
>.
</P
></DD
><DT
><A
NAME="GUC-TIMEZONE"
></A
><TT
CLASS="VARNAME"
>timezone</TT
> (<TT
CLASS="TYPE"
>string</TT
>)</DT
><DD
><P
> Sets the time zone for displaying and interpreting time
stamps. The default is 'unknown', which means to use whatever
the system environment specifies as the time zone. See <A
HREF="datatype-datetime.html"
>Section 8.5</A
> for more information.
</P
></DD
><DT
><A
NAME="GUC-AUSTRALIAN-TIMEZONES"
></A
><TT
CLASS="VARNAME"
>australian_timezones</TT
> (<TT
CLASS="TYPE"
>boolean</TT
>)</DT
><DD
><P
> If set to on, <TT
CLASS="LITERAL"
>ACST</TT
>,
<TT
CLASS="LITERAL"
>CST</TT
>, <TT
CLASS="LITERAL"
>EST</TT
>, and
<TT
CLASS="LITERAL"
>SAT</TT
> are interpreted as Australian time
zones rather than as North/South American time zones and
Saturday. The default is <TT
CLASS="LITERAL"
>off</TT
>.
</P
></DD
><DT
><A
NAME="GUC-EXTRA-FLOAT-DIGITS"
></A
><TT
CLASS="VARNAME"
>extra_float_digits</TT
> (<TT
CLASS="TYPE"
>integer</TT
>)</DT
><DD
><P
> This parameter adjusts the number of digits displayed for
floating-point values, including <TT
CLASS="TYPE"
>float4</TT
>, <TT
CLASS="TYPE"
>float8</TT
>,
and geometric data types. The parameter value is added to the
standard number of digits (<TT
CLASS="LITERAL"
>FLT_DIG</TT
> or <TT
CLASS="LITERAL"
>DBL_DIG</TT
>
as appropriate). The value can be set as high as 2, to include
partially-significant digits; this is especially useful for dumping
float data that needs to be restored exactly. Or it can be set
negative to suppress unwanted digits.
</P
></DD
><DT
><A
NAME="GUC-CLIENT-ENCODING"
></A
><TT
CLASS="VARNAME"
>client_encoding</TT
> (<TT
CLASS="TYPE"
>string</TT
>)</DT
><DD
><P
> Sets the client-side encoding (character set).
The default is to use the database encoding.
</P
></DD
><DT
><A
NAME="GUC-LC-MESSAGES"
></A
><TT
CLASS="VARNAME"
>lc_messages</TT
> (<TT
CLASS="TYPE"
>string</TT
>)</DT
><DD
><P
> Sets the language in which messages are displayed. Acceptable
values are system-dependent; see <A
HREF="charset.html#LOCALE"
>Section 21.1</A
> for
more information. If this variable is set to the empty string
(which is the default) then the value is inherited from the
execution environment of the server in a system-dependent way.
</P
><P
> On some systems, this locale category does not exist. Setting
this variable will still work, but there will be no effect.
Also, there is a chance that no translated messages for the
desired language exist. In that case you will continue to see
the English messages.
</P
></DD
><DT
><A
NAME="GUC-LC-MONETARY"
></A
><TT
CLASS="VARNAME"
>lc_monetary</TT
> (<TT
CLASS="TYPE"
>string</TT
>)</DT
><DD
><P
> Sets the locale to use for formatting monetary amounts, for
example with the <CODE
CLASS="FUNCTION"
>to_char</CODE
> family of
functions. Acceptable values are system-dependent; see <A
HREF="charset.html#LOCALE"
>Section 21.1</A
> for more information. If this variable is
set to the empty string (which is the default) then the value
is inherited from the execution environment of the server in a
system-dependent way.
</P
></DD
><DT
><A
NAME="GUC-LC-NUMERIC"
></A
><TT
CLASS="VARNAME"
>lc_numeric</TT
> (<TT
CLASS="TYPE"
>string</TT
>)</DT
><DD
><P
> Sets the locale to use for formatting numbers, for example
with the <CODE
CLASS="FUNCTION"
>to_char</CODE
> family of
functions. Acceptable values are system-dependent; see <A
HREF="charset.html#LOCALE"
>Section 21.1</A
> for more information. If this variable is
set to the empty string (which is the default) then the value
is inherited from the execution environment of the server in a
system-dependent way.
</P
></DD
><DT
><A
NAME="GUC-LC-TIME"
></A
><TT
CLASS="VARNAME"
>lc_time</TT
> (<TT
CLASS="TYPE"
>string</TT
>)</DT
><DD
><P
> Sets the locale to use for formatting date and time values.
(Currently, this setting does nothing, but it may in the
future.) Acceptable values are system-dependent; see <A
HREF="charset.html#LOCALE"
>Section 21.1</A
> for more information. If this variable is
set to the empty string (which is the default) then the value
is inherited from the execution environment of the server in a
system-dependent way.
</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="RUNTIME-CONFIG-CLIENT-OTHER"
>17.10.3. Other Defaults</A
></H2
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="GUC-EXPLAIN-PRETTY-PRINT"
></A
><TT
CLASS="VARNAME"
>explain_pretty_print</TT
> (<TT
CLASS="TYPE"
>boolean</TT
>)</DT
><DD
><P
> Determines whether <TT
CLASS="COMMAND"
>EXPLAIN VERBOSE</TT
> uses the
indented or non-indented format for displaying detailed
query-tree dumps. The default is <TT
CLASS="LITERAL"
>on</TT
>.
</P
></DD
><DT
><A
NAME="GUC-DYNAMIC-LIBRARY-PATH"
></A
><TT
CLASS="VARNAME"
>dynamic_library_path</TT
> (<TT
CLASS="TYPE"
>string</TT
>)</DT
><DD
><P
> If a dynamically loadable module needs to be opened and the
file name specified in the <TT
CLASS="COMMAND"
>CREATE FUNCTION</TT
> or
<TT
CLASS="COMMAND"
>LOAD</TT
> command
does not have a directory component (i.e. the
name does not contain a slash), the system will search this
path for the required file.
</P
><P
> The value for <TT
CLASS="VARNAME"
>dynamic_library_path</TT
> has to be a
list of absolute directory paths separated by colons (or semi-colons
on Windows). If a list element starts
with the special string <TT
CLASS="LITERAL"
>$libdir</TT
>, the
compiled-in <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> package
library directory is substituted for <TT
CLASS="LITERAL"
>$libdir</TT
>. This
is where the modules provided by the standard
<SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> distribution are installed.
(Use <TT
CLASS="LITERAL"
>pg_config --pkglibdir</TT
> to find out the name of
this directory.) For example:
</P><PRE
CLASS="PROGRAMLISTING"
>dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir'</PRE
><P>
or, in a Windows environment:
</P><PRE
CLASS="PROGRAMLISTING"
>dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'</PRE
><P>
</P
><P
> The default value for this parameter is
<TT
CLASS="LITERAL"
>'$libdir'</TT
>. If the value is set to an empty
string, the automatic path search is turned off.
</P
><P
> This parameter can be changed at run time by superusers, but a
setting done that way will only persist until the end of the
client connection, so this method should be reserved for
development purposes. The recommended way to set this parameter
is in the <TT
CLASS="FILENAME"
>postgresql.conf</TT
> configuration
file.
</P
></DD
></DL
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="runtime-config-autovacuum.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="runtime-config-locks.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Automatic Vacuuming</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="runtime-config.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Lock Management</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>