Terence,
Thanks for quick reply, I read your thread (Dec, 2012) before posting my qu=
estion.
But, recompile is not an option for me. Was hoping, that something regardi=
ng this issue changed since...
Igor Neyman
From: Terence Ferraro [mailto:terencejferraro@gmail.com]
Sent: Wednesday, February 06, 2013 1:45 PM
To: Igor Neyman
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] configuring timezone
See the archived thread here: http://www.postgresql.org/message-id/CAEghcWD=
8DXjroBYCZsdGrx+cHTCbCbW9es2uQ+o7a8NZ61JT=3DQ@mail.gmail.com
Short version: Sorry, but you're going to need to recompile if you want tha=
t behavior. Here's a diff applied against 9.2.1 http://pastebin.com/5AyaX2R=
F. I've deployed the patched version a couple dozen times now and it is wor=
king flawlessly.
T.J.
On Wed, Feb 6, 2013 at 1:32 PM, Igor Neyman <ineyman@perceptron.com<mailto:=
ineyman@perceptron.com>> wrote:
Timezone configuration parameter (defaulting to system timezone) worked fi=
ne for us before upgrading from 8.4. to 9.2.
Now we've got a problem.
9.2 Release Notes says:
* Identify the server time zone during initdb, and set postgresql.conf ent=
ries timezone<http://www.postgresql.org/docs/9.2/static/runtime-config-clie=
nt.html#GUC-TIMEZONE> and log_timezone<http://www.postgresql.org/docs/9.2/s=
tatic/runtime-config-logging.html#GUC-LOG-TIMEZONE> accordingly (Tom Lane)
This avoids expensive time zone probes during server start.
Question: is there any way to revert back to old behavior so that server wi=
ll probe system's timezone on startup (default to OS timezone on startup) i=
nstead setting it during initdb?
Obviously, without recompiling/rebuilding Postgres.
I'm dealing with the situation, where system is being built in one timezone=
(could be anywhere around the globe), and then moved to other (not known d=
uring system build) location with different timezone.
After relocation, OS timezone will change, but we can't allow user to edit =
timezone parameter in Postgresql.conf.
Regards,
Igor Neyman
