diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2011-09-09 17:59:11 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2011-09-09 17:59:11 -0400 |
| commit | ca4af308c32d03db5fbacb54d6e583ceb904f268 (patch) | |
| tree | 352fb06319a1c8e3efd78acaca9cc8b8ff0e7eda /doc/src/sgml/ref | |
| parent | a7801b62f21bd051444bd1119cd3745ecc8e14ec (diff) | |
Simplify handling of the timezone GUC by making initdb choose the default.
We were doing some amazingly complicated things in order to avoid running
the very expensive identify_system_timezone() procedure during GUC
initialization. But there is an obvious fix for that, which is to do it
once during initdb and have initdb install the system-specific default into
postgresql.conf, as it already does for most other GUC variables that need
system-environment-dependent defaults. This means that the timezone (and
log_timezone) settings no longer have any magic behavior in the server.
Per discussion.
Diffstat (limited to 'doc/src/sgml/ref')
| -rw-r--r-- | doc/src/sgml/ref/set.sgml | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/doc/src/sgml/ref/set.sgml b/doc/src/sgml/ref/set.sgml index 40e1bd4e607..21745db4627 100644 --- a/doc/src/sgml/ref/set.sgml +++ b/doc/src/sgml/ref/set.sgml @@ -239,9 +239,7 @@ SELECT setseed(<replaceable>value</replaceable>); <listitem> <para> Set the time zone to your local time zone (that is, the - server's default value of <varname>timezone</>; if this - has not been explicitly set anywhere, it will be the zone that - the server's operating system defaults to). + server's default value of <varname>timezone</>). </para> </listitem> </varlistentry> |