| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Laurent Laborde <kerdezixe(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: timezone change not in changelog ? |
| Date: | 2012-10-17 13:51:17 |
| Message-ID: | 19317.1350481877@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Laurent Laborde <kerdezixe(at)gmail(dot)com> writes:
> Friendly greetings !
> There is a change between 9.1 and 9.2 that doesn't seems to be in the
> changelog :
> http://www.postgresql.org/docs/9.2/static/runtime-config-client.html#GUC-TIMEZONE
> http://www.postgresql.org/docs/9.1/static/runtime-config-client.html#GUC-TIMEZONE
ITYM this:
<listitem>
<para>
Identify the server time zone during <application>initdb</>, and set
<filename>postgresql.conf</filename> entries
<link linkend="guc-timezone"><varname>timezone</></link> and
<link linkend="guc-log-timezone"><varname>log_timezone</></link>
accordingly (Tom Lane)
</para>
<para>
This avoids expensive time zone probes during server start.
</para>
</listitem>
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2012-10-17 13:53:44 | Re: [PATCH] Enforce that INSERT...RETURNING preserves the order of multi rows |
| Previous Message | Andrew Dunstan | 2012-10-17 13:19:58 | Re: Doc patch "only relevant" -> "relevant only" |