From: | Igor Neyman <ineyman(at)perceptron(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: configuring timezone |
Date: | 2013-02-07 02:47:46 |
Message-ID: | A76B25F2823E954C9E45E32FA49D70EC08F78AE8@mail.corp.perceptron.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thank you for explaining.
Regards,
Igor Neyman
________________________________________
From: Tom Lane [tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Wednesday, February 06, 2013 5:11 PM
To: Igor Neyman
Cc: Adrian Klaver; pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] configuring timezone
Igor Neyman <ineyman(at)perceptron(dot)com> writes:
> Going back to the reason for this change in Release Notes:
> "This avoids expensive time zone probes during server start."
> How expensive?
The time zone probe logic involves reading every file under
/usr/share/zoneinfo (or wherever you have the Olson tz database
installed). There are a couple thousand of those in a typical Linux
installation. In a cold-boot situation where none of that data is
already swapped in, it's not unusual for this to take five seconds or
more. Now that may or may not seem like a lot, but it's more than
enough to cause many startup scripts to conclude that the postmaster has
failed. The hacks we'd built up to deal with this eventually became
insupportable.
We're not going back. I suggest you consider ways to adjust your
server-migration process.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Gurjeet Singh | 2013-02-07 03:00:28 | Re: [HACKERS] function for setting/getting same timestamp during whole transaction |
Previous Message | Zach Seaman | 2013-02-07 00:56:29 | Problems with ñ and tildes / CSV import problems in PostgreSQL 9.1 |