Re: configuring timezone - Mailing list pgsql-general
From | Igor Neyman |
---|---|
Subject | Re: configuring timezone |
Date | |
Msg-id | A76B25F2823E954C9E45E32FA49D70EC08F78D40@mail.corp.perceptron.com Whole thread Raw |
In response to | Re: configuring timezone (Terence Ferraro <terencejferraro@gmail.com>) |
List | pgsql-general |
Terence, Thank you for the offer. But, I will probably be creating custom install scripts to run at destinati= on location to modify parameter in Postgresql.conf. Regards, Igor Neyman From: Terence Ferraro [mailto:terencejferraro@gmail.com] Sent: Wednesday, February 06, 2013 6:47 PM To: Igor Neyman Cc: pgsql-general@postgresql.org Subject: Re: configuring timezone 9.2.1 was the version standard when I was building and deploying...so no, I= probably will not (personally) be updating anytime soon... However, if you're interested, I'll see if I can find a place tonight or to= morrow to put these binaries (they are 32-bit as well), source, etc (source= forge maybe?). I can also include to inno setup script that builds an insta= ller similar to the EnterpriseDB version; that is, it automatices the servi= ce setup, creates a postgres user, etc. Hell, I may as well include the pre= -built installer, too, if you don't want to customize anything.. In addition to the timezone fix, I (originally) wanted to build my own Wind= ows installer because the EnterpriseDB version does NOT link against zlib w= ith respect to openssl. In other words, no compressed ssl connections are p= ossible with the currently distributed windows version. This one is linked = against zlib (and the speed increase is quite significant). T.J. On Wed, Feb 6, 2013 at 3:23 PM, Igor Neyman <ineyman@perceptron.com<mailto:= ineyman@perceptron.com>> wrote: I am on Windows (both 32 and 64 bit) using 32-bit Postgres. So, your binaries are for 9.2.1, you aren't planning to go to 9.2.2? From: Terence Ferraro [mailto:terencejferraro@gmail.com<mailto:terencejferr= aro@gmail.com>] Sent: Wednesday, February 06, 2013 3:07 PM To: Igor Neyman Cc: pgsql-general@postgresql.org<mailto:pgsql-general@postgresql.org> Subject: Re: [GENERAL] configuring timezone Sorry, but from what I understand the change is permanent. If recompile is = not an option but you're on Windows let me know; I do have binaries availab= le.. On Wed, Feb 6, 2013 at 2:05 PM, Igor Neyman <ineyman@perceptron.com<mailto:= ineyman@perceptron.com>> wrote: 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<mailto:terencejferr= aro@gmail.com>] Sent: Wednesday, February 06, 2013 1:45 PM To: Igor Neyman Cc: pgsql-general@postgresql.org<mailto: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
pgsql-general by date: