From: | Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Regarding timezone |
Date: | 2014-09-17 14:53:34 |
Message-ID: | CALSLE1PqH5+6eQUCSYtFwov7xWi3i4OqFrLWJYQhH9PwrBCsdg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Sep 17, 2014 at 7:24 PM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)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.
Regards..
From | Date | Subject | |
---|---|---|---|
Next Message | Dev Kumkar | 2014-09-17 14:54:42 | Re: [SQL] pg_multixact issues |
Previous Message | Adrian Klaver | 2014-09-17 14:40:49 | Re: encoding confusion with \copy command |