From: | "Leonardo M(dot) Ramé" <l(dot)rame(at)griensu(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Timezone mismatch |
Date: | 2015-03-20 17:55:21 |
Message-ID: | 550C5F09.20406@griensu.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
El 20/03/15 a las 14:11, "Leonardo M. Ramé" escibió:
> El 20/03/15 a las 13:03, Adrian Klaver escibió:
>> I am not sure what the exact issue is?
>>
>> How are you determining that the new time zone is not being used?
>>
>> What was the old time zone, what is the new one?
> I don't know if the new time zone is beign used, It just coincede with
> the old local time zone which was -3 hours compared to UTC.
>
> Old time zone was:
>
> Current default time zone: 'America/Argentina/Cordoba'
> Local time is now: Fri Mar 20 06:46:58 ART 2015.
> Universal Time is now: Fri Mar 20 09:46:58 UTC 2015.
>
> New time zone is:
>
> Current default time zone: 'Etc/UTC'
> Local time is now: Fri Mar 20 09:47:48 UTC 2015.
> Universal Time is now: Fri Mar 20 09:47:48 UTC 2015.
>
>
Well, pg_load_conf didn't reoload the timezone config from
postgresql.conf, I had to restart the service to be changed.
Leonardo.
From | Date | Subject | |
---|---|---|---|
Next Message | Vick Khera | 2015-03-20 17:57:32 | Re: Timezone mismatch |
Previous Message | Leonardo M. Ramé | 2015-03-20 17:21:54 | Re: Sequences not created, bug in pg_dump? |