1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
5
>Client Connection Defaults</TITLE
8
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10
HREF="mailto:pgsql-docs@postgresql.org"><LINK
12
TITLE="PostgreSQL 9.1beta1 Documentation"
13
HREF="index.html"><LINK
15
TITLE="Server Configuration"
16
HREF="runtime-config.html"><LINK
18
TITLE="Automatic Vacuuming"
19
HREF="runtime-config-autovacuum.html"><LINK
21
TITLE="Lock Management"
22
HREF="runtime-config-locks.html"><LINK
25
HREF="stylesheet.css"><META
26
HTTP-EQUIV="Content-Type"
27
CONTENT="text/html; charset=ISO-8859-1"><META
29
CONTENT="2011-04-27T21:20:33"></HEAD
35
SUMMARY="Header navigation table"
47
>PostgreSQL 9.1beta1 Documentation</A
56
TITLE="Automatic Vacuuming"
57
HREF="runtime-config-autovacuum.html"
66
TITLE="Server Configuration"
67
HREF="runtime-config.html"
74
>Chapter 18. Server Configuration</TD
80
TITLE="Server Configuration"
81
HREF="runtime-config.html"
89
TITLE="Lock Management"
90
HREF="runtime-config-locks.html"
104
NAME="RUNTIME-CONFIG-CLIENT"
105
>18.10. Client Connection Defaults</A
112
NAME="RUNTIME-CONFIG-CLIENT-STATEMENT"
113
>18.10.1. Statement Behavior</A
122
NAME="GUC-SEARCH-PATH"
133
> This variable specifies the order in which schemas are searched
134
when an object (table, data type, function, etc.) is referenced by a
135
simple name with no schema specified. When there are objects of
136
identical names in different schemas, the one found first
137
in the search path is used. An object that is not in any of the
138
schemas in the search path can only be referenced by specifying
139
its containing schema with a qualified (dotted) name.
145
> must be a comma-separated
146
list of schema names. If one of the list items is
147
the special value <TT
151
having the name returned by <CODE
154
> is substituted, if there
155
is such a schema. (If not, <TT
161
> The system catalog schema, <TT
165
searched, whether it is mentioned in the path or not. If it is
166
mentioned in the path then it will be searched in the specified
170
> is not in the path then it will
177
> searching any of the path items.
180
> Likewise, the current session's temporary-table schema,
189
>, is always searched if it
190
exists. It can be explicitly listed in the path by using the
194
>. If it is not listed in the path then
195
it is searched first (even before <TT
199
the temporary schema is only searched for relation (table, view,
200
sequence, etc) and data type names. It is never searched for
201
function or operator names.
204
> When objects are created without specifying a particular target
205
schema, they will be placed in the first schema listed
206
in the search path. An error is reported if the search path is
210
> The default value for this parameter is
213
>'"$user", public'</TT
214
> (where the second part will be
215
ignored if there is no schema named <TT
219
This supports shared use of a database (where no users
220
have private schemas, and all share use of <TT
224
private per-user schemas, and combinations of these. Other
225
effects can be obtained by altering the default search path
226
setting, either globally or per-user.
229
> The current effective value of the search path can be examined
236
>current_schemas()</CODE
237
>. This is not quite the same as
238
examining the value of <TT
244
>current_schemas()</CODE
245
> shows how the items
252
> For more information on schema handling, see <A
253
HREF="ddl-schemas.html"
260
NAME="GUC-DEFAULT-TABLESPACE"
264
>default_tablespace</TT
271
> This variable specifies the default tablespace in which to create
272
objects (tables and indexes) when a <TT
276
not explicitly specify a tablespace.
279
> The value is either the name of a tablespace, or an empty string
280
to specify using the default tablespace of the current database.
281
If the value does not match the name of any existing tablespace,
285
> will automatically use the default
286
tablespace of the current database. If a nondefault tablespace
287
is specified, the user must have <TT
291
for it, or creation attempts will fail.
294
> This variable is not used for temporary tables; for them,
296
HREF="runtime-config-client.html#GUC-TEMP-TABLESPACES"
298
> is consulted instead.
301
> This variable is also not used when creating databases.
302
By default, a new database inherits its tablespace setting from
303
the template database it is copied from.
306
> For more information on tablespaces,
308
HREF="manage-ag-tablespaces.html"
315
NAME="GUC-TEMP-TABLESPACES"
319
>temp_tablespaces</TT
326
> This variable specifies tablespaces in which to create temporary
327
objects (temp tables and indexes on temp tables) when a
331
> command does not explicitly specify a tablespace.
332
Temporary files for purposes such as sorting large data sets
333
are also created in these tablespaces.
336
> The value is a list of names of tablespaces. When there is more than
337
one name in the list, <SPAN
341
member of the list each time a temporary object is to be created;
342
except that within a transaction, successively created temporary
343
objects are placed in successive tablespaces from the list.
344
If the selected element of the list is an empty string,
348
> will automatically use the default
349
tablespace of the current database instead.
354
>temp_tablespaces</TT
355
> is set interactively, specifying a
356
nonexistent tablespace is an error, as is specifying a tablespace for
357
which the user does not have <TT
360
> privilege. However,
361
when using a previously set value, nonexistent tablespaces are
362
ignored, as are tablespaces for which the user lacks
366
> privilege. In particular, this rule applies when
367
using a value set in <TT
373
> The default value is an empty string, which results in all temporary
374
objects being created in the default tablespace of the current
379
HREF="runtime-config-client.html#GUC-DEFAULT-TABLESPACE"
380
>default_tablespace</A
386
NAME="GUC-CHECK-FUNCTION-BODIES"
390
>check_function_bodies</TT
397
> This parameter is normally on. When set to <TT
401
disables validation of the function body string during <A
402
HREF="sql-createfunction.html"
404
>. Disabling validation is
405
occasionally useful to avoid problems such as forward references
406
when restoring function definitions from a dump.
411
NAME="GUC-DEFAULT-TRANSACTION-ISOLATION"
415
>default_transaction_isolation</TT
422
> Each SQL transaction has an isolation level, which can be
425
>"read uncommitted"</SPAN
432
>"repeatable read"</SPAN
436
>"serializable"</SPAN
437
>. This parameter controls the
438
default isolation level of each new transaction. The default
441
>"read committed"</SPAN
449
HREF="sql-set-transaction.html"
451
> for more information.
456
NAME="GUC-DEFAULT-TRANSACTION-READ-ONLY"
460
>default_transaction_read_only</TT
467
> A read-only SQL transaction cannot alter non-temporary tables.
468
This parameter controls the default read-only status of each new
469
transaction. The default is <TT
476
HREF="sql-set-transaction.html"
478
> for more information.
483
NAME="GUC-DEFAULT-TRANSACTION-DEFERRABLE"
487
>default_transaction_deferrable</TT
494
> When running at the <TT
498
a deferrable read-only SQL transaction may be delayed before
499
it is allowed to proceed. However, once it begins executing
500
it does not incur any of the overhead required to ensure
501
serializability; so serialization code will have no reason to
502
force it to abort because of concurrent updates, making this
503
option suitable for long-running read-only transactions.
506
> This parameter controls the default deferrable status of each
507
new transaction. It currently has no effect on read-write
508
transactions or those operating at isolation levels lower
512
>. The default is <TT
519
HREF="sql-set-transaction.html"
521
> for more information.
526
NAME="GUC-SESSION-REPLICATION-ROLE"
530
>session_replication_role</TT
537
> Controls firing of replication-related triggers and rules for the
538
current session. Setting this variable requires
539
superuser privilege and results in discarding any previously cached
540
query plans. Possible values are <TT
552
HREF="sql-altertable.html"
560
NAME="GUC-STATEMENT-TIMEOUT"
564
>statement_timeout</TT
571
> Abort any statement that takes over the specified number of
572
milliseconds, starting from the time the command arrives at the server
573
from the client. If <TT
575
>log_min_error_statement</TT
580
> or lower, the statement that timed out will also be
581
logged. A value of zero (the default) turns this off.
586
>statement_timeout</TT
591
> is not recommended because it
592
affects all sessions.
597
NAME="GUC-VACUUM-FREEZE-TABLE-AGE"
601
>vacuum_freeze_table_age</TT
611
> performs a whole-table scan if the table's
619
the age specified by this setting. The default is 150 million
620
transactions. Although users can set this value anywhere from zero to
624
> will silently limit the effective value
626
HREF="runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE"
627
>autovacuum_freeze_max_age</A
629
periodical manual <TT
632
> has a chance to run before an
633
anti-wraparound autovacuum is launched for the table. For more
636
HREF="routine-vacuuming.html#VACUUM-FOR-WRAPAROUND"
643
NAME="GUC-VACUUM-FREEZE-MIN-AGE"
647
>vacuum_freeze_min_age</TT
654
> Specifies the cutoff age (in transactions) that <TT
658
should use to decide whether to replace transaction IDs with
662
> while scanning a table.
663
The default is 50 million transactions. Although
664
users can set this value anywhere from zero to one billion,
668
> will silently limit the effective value to half
670
HREF="runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE"
671
>autovacuum_freeze_max_age</A
673
that there is not an unreasonably short time between forced
674
autovacuums. For more information see <A
675
HREF="routine-vacuuming.html#VACUUM-FOR-WRAPAROUND"
682
NAME="GUC-BYTEA-OUTPUT"
693
> Sets the output format for values of type <TT
704
> (the traditional PostgreSQL
706
HREF="datatype-binary.html"
713
accepts both formats on input, regardless of this setting.
729
> Sets how binary values are to be encoded in XML. This applies
733
> values are converted to
734
XML by the functions <CODE
741
>. Possible values are
749
are both defined in the XML Schema standard. The default is
753
>. For further information about
754
XML-related functions, see <A
755
HREF="functions-xml.html"
760
> The actual choice here is mostly a matter of taste,
761
constrained only by possible restrictions in client
762
applications. Both methods support all possible values,
763
although the hex encoding will be somewhat larger than the
787
> is implicit when converting between
788
XML and character string values. See <A
789
HREF="datatype-xml.html"
791
> for a description of this. Valid
806
> According to the SQL standard, the command to set this option is
809
>SET XML OPTION { DOCUMENT | CONTENT };</PRE
811
This syntax is also available in PostgreSQL.
822
NAME="RUNTIME-CONFIG-CLIENT-FORMAT"
823
>18.10.2. Locale and Formatting</A
843
> Sets the display format for date and time values, as well as the
844
rules for interpreting ambiguous date input values. For
845
historical reasons, this variable contains two independent
846
components: the output format specification (<TT
860
and the input/output specification for year/month/day ordering
871
can be set separately or together. The keywords <TT
878
> are synonyms for <TT
892
> are synonyms for <TT
897
HREF="datatype-datetime.html"
899
> for more information. The
900
built-in default is <TT
907
> will initialize the
908
configuration file with a setting that corresponds to the
909
behavior of the chosen <TT
917
NAME="GUC-INTERVALSTYLE"
928
> Sets the display format for interval values.
933
output matching <ACRONYM
936
> standard interval literals.
940
> (which is the default) will produce
941
output matching <SPAN
944
> releases prior to 8.4
946
HREF="runtime-config-client.html#GUC-DATESTYLE"
949
parameter was set to <TT
955
>postgres_verbose</TT
956
> will produce output
960
> releases prior to 8.4
965
parameter was set to non-<TT
972
> will produce output matching the time
975
>"format with designators"</SPAN
983
> parameter also affects the
984
interpretation of ambiguous interval input. See
986
HREF="datatype-datetime.html#DATATYPE-INTERVAL-INPUT"
988
> for more information.
1004
> Sets the time zone for displaying and interpreting time stamps.
1008
>, which means to use whatever
1009
the system environment specifies as the time zone. See <A
1010
HREF="datatype-datetime.html#DATATYPE-TIMEZONES"
1018
NAME="GUC-TIMEZONE-ABBREVIATIONS"
1022
>timezone_abbreviations</TT
1029
> Sets the collection of time zone abbreviations that will be accepted
1030
by the server for datetime input. The default is <TT
1034
which is a collection that works in most of the world; there are
1035
also 'Australia' and 'India', and other collections can be defined
1036
for a particular installation. See <A
1037
HREF="datetime-appendix.html"
1039
> for more information.
1044
NAME="GUC-EXTRA-FLOAT-DIGITS"
1048
>extra_float_digits</TT
1055
> This parameter adjusts the number of digits displayed for
1056
floating-point values, including <TT
1063
and geometric data types. The parameter value is added to the
1064
standard number of digits (<TT
1071
as appropriate). The value can be set as high as 3, to include
1072
partially-significant digits; this is especially useful for dumping
1073
float data that needs to be restored exactly. Or it can be set
1074
negative to suppress unwanted digits.
1079
NAME="GUC-CLIENT-ENCODING"
1083
>client_encoding</TT
1090
> Sets the client-side encoding (character set).
1091
The default is to use the database encoding.
1092
The character sets supported by the <SPAN
1096
server are described in <A
1097
HREF="multibyte.html#MULTIBYTE-CHARSET-SUPPORTED"
1104
NAME="GUC-LC-MESSAGES"
1115
> Sets the language in which messages are displayed. Acceptable
1116
values are system-dependent; see <A
1120
more information. If this variable is set to the empty string
1121
(which is the default) then the value is inherited from the
1122
execution environment of the server in a system-dependent way.
1125
> On some systems, this locale category does not exist. Setting
1126
this variable will still work, but there will be no effect.
1127
Also, there is a chance that no translated messages for the
1128
desired language exist. In that case you will continue to see
1129
the English messages.
1132
> Only superusers can change this setting, because it affects the
1133
messages sent to the server log as well as to the client, and
1134
an improper value might obscure the readability of the server
1140
NAME="GUC-LC-MONETARY"
1151
> Sets the locale to use for formatting monetary amounts, for
1152
example with the <CODE
1156
functions. Acceptable values are system-dependent; see <A
1159
> for more information. If this variable is
1160
set to the empty string (which is the default) then the value
1161
is inherited from the execution environment of the server in a
1162
system-dependent way.
1167
NAME="GUC-LC-NUMERIC"
1178
> Sets the locale to use for formatting numbers, for example
1183
functions. Acceptable values are system-dependent; see <A
1186
> for more information. If this variable is
1187
set to the empty string (which is the default) then the value
1188
is inherited from the execution environment of the server in a
1189
system-dependent way.
1205
> Sets the locale to use for formatting dates and times, for example
1210
functions. Acceptable values are system-dependent; see <A
1213
> for more information. If this variable is
1214
set to the empty string (which is the default) then the value
1215
is inherited from the execution environment of the server in a
1216
system-dependent way.
1221
NAME="GUC-DEFAULT-TEXT-SEARCH-CONFIG"
1225
>default_text_search_config</TT
1232
> Selects the text search configuration that is used by those variants
1233
of the text search functions that do not have an explicit argument
1234
specifying the configuration.
1236
HREF="textsearch.html"
1238
> for further information.
1239
The built-in default is <TT
1241
>pg_catalog.simple</TT
1246
> will initialize the
1247
configuration file with a setting that corresponds to the
1251
> locale, if a configuration
1252
matching that locale can be identified.
1263
NAME="RUNTIME-CONFIG-CLIENT-OTHER"
1264
>18.10.3. Other Defaults</A
1269
CLASS="VARIABLELIST"
1273
NAME="GUC-DYNAMIC-LIBRARY-PATH"
1277
>dynamic_library_path</TT
1284
> If a dynamically loadable module needs to be opened and the
1285
file name specified in the <TT
1287
>CREATE FUNCTION</TT
1293
does not have a directory component (i.e., the
1294
name does not contain a slash), the system will search this
1295
path for the required file.
1300
>dynamic_library_path</TT
1302
list of absolute directory paths separated by colons (or semi-colons
1303
on Windows). If a list element starts
1304
with the special string <TT
1312
library directory is substituted for <TT
1316
is where the modules provided by the standard
1320
> distribution are installed.
1323
>pg_config --pkglibdir</TT
1324
> to find out the name of
1325
this directory.) For example:
1327
CLASS="PROGRAMLISTING"
1328
>dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir'</PRE
1330
or, in a Windows environment:
1332
CLASS="PROGRAMLISTING"
1333
>dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'</PRE
1337
> The default value for this parameter is
1341
>. If the value is set to an empty
1342
string, the automatic path search is turned off.
1345
> This parameter can be changed at run time by superusers, but a
1346
setting done that way will only persist until the end of the
1347
client connection, so this method should be reserved for
1348
development purposes. The recommended way to set this parameter
1351
>postgresql.conf</TT
1358
NAME="GUC-GIN-FUZZY-SEARCH-LIMIT"
1362
>gin_fuzzy_search_limit</TT
1369
> Soft upper limit of the size of the set returned by GIN index scans. For more
1371
HREF="gin-tips.html"
1378
NAME="GUC-LOCAL-PRELOAD-LIBRARIES"
1382
>local_preload_libraries</TT
1389
> This variable specifies one or more shared libraries that are
1390
to be preloaded at connection start. If more than one library
1391
is to be loaded, separate their names with commas. All library
1392
names are converted to lower case unless double-quoted.
1393
This parameter cannot be changed after the start of a particular
1397
> Because this is not a superuser-only option, the libraries
1398
that can be loaded are restricted to those appearing in the
1402
> subdirectory of the installation's
1403
standard library directory. (It is the database administrator's
1404
responsibility to ensure that only <SPAN
1408
are installed there.) Entries in <TT
1410
>local_preload_libraries</TT
1412
can specify this directory explicitly, for example
1415
>$libdir/plugins/mylib</TT
1417
the library name — <TT
1421
the same effect as <TT
1423
>$libdir/plugins/mylib</TT
1429
>local_preload_libraries</TT
1431
performance advantage to loading a library at session
1432
start rather than when it is first used. Rather, the intent of
1433
this feature is to allow debugging or performance-measurement
1434
libraries to be loaded into specific sessions without an explicit
1438
> command being given. For example, debugging could
1439
be enabled for all sessions under a given user name by setting
1440
this parameter with <TT
1446
> If a specified library is not found,
1447
the connection attempt will fail.
1450
> Every PostgreSQL-supported library has a <SPAN
1454
> that is checked to guarantee compatibility.
1455
For this reason, non-PostgreSQL libraries cannot be
1468
SUMMARY="Footer navigation table"
1479
HREF="runtime-config-autovacuum.html"
1497
HREF="runtime-config-locks.html"
1507
>Automatic Vacuuming</TD
1513
HREF="runtime-config.html"
1521
>Lock Management</TD
b'\\ No newline at end of file'
added
removed
doc/src/sgml/html/runtime-config-client.html
