On 09/17/2014 07:53 AM, Dev Kumkar wrote:
On Wed, Sep 17, 2014 at 7:24 PM, Adrian Klaver <adrian.kla...@aklaver.com <mailto:adrian.kla...@aklaver.com>> wrote:So you will need to determine what method you binaries use. If they are using the system timezone data, you will need to update that. Thanks! Just a hack here, how about copying "pgsql/share/postgresql/timezone/Etc/GMT-3" as "pgsql/share/postgresql/timezone/Europe/Moscow" This will make the *pg_timezone_names()* function to return output as follows: >> "Europe/Moscow";"GMT-3";"03:00:00";f With this "now()" function returns expected data for Moscow timezone. Please let me know your comments here.
I am not that versed in the timezone handling to make a definitive statement. I would say it should work until you upgrade. At that point the new Moscow timezone should be correct and the change will not matter. I would verify on the upgrade though.
Regards..
-- Adrian Klaver adrian.kla...@aklaver.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
