|
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@xxxxxxxxx]
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 available.. On Wed, Feb 6, 2013 at 2:05 PM, Igor Neyman <ineyman@xxxxxxxxxxxxxx> wrote: Terence, Thanks for quick reply, I read your thread (Dec, 2012) before posting my question. But, recompile is not an option for me. Was hoping, that something regarding this issue changed
since… Igor Neyman From: Terence Ferraro [mailto:terencejferraro@xxxxxxxxx]
See the archived thread here:
http://www.postgresql.org/message-id/CAEghcWD8DXjroBYCZsdGrx+cHTCbCbW9es2uQ+o7a8NZ61JT=Q@xxxxxxxxxxxxxx On Wed, Feb 6, 2013 at 1:32 PM, Igor Neyman <ineyman@xxxxxxxxxxxxxx> wrote: Timezone configuration parameter (defaulting to system timezone) worked fine 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 entries
timezone and
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 will probe system’s timezone on startup (default to OS timezone on startup) instead 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 during 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 |
