On Thu, Sep 24, 2015 at 5:22 PM, Adrian Klaver
wrote:
> Yeah, I forgot about the EXTRACT change.
>
>
>> regards, tom lane
>>
>>
>
thanks a lot for clarifying!
--
Willy-Bas Loos
On 09/24/2015 08:08 AM, Tom Lane wrote:
Adrian Klaver writes:
On 09/24/2015 07:01 AM, Willy-Bas Loos wrote:
=# show timezone;
TimeZone
---
localtime
(1 row)
This sounded familiar:
http://www.postgresql.org/message-id/m3616t3m5d@carbon.jhcloos.org
Yeah ... we never did figure o
Adrian Klaver writes:
> On 09/24/2015 07:01 AM, Willy-Bas Loos wrote:
>> =# show timezone;
>> TimeZone
>> ---
>> localtime
>> (1 row)
> This sounded familiar:
> http://www.postgresql.org/message-id/m3616t3m5d@carbon.jhcloos.org
Yeah ... we never did figure out what was producing that
Willy-Bas Loos writes:
> Is there a reason for this change of behavior between 8.4 and 9.* ?
See the "incompatibilities" section in the 9.2 release notes:
* Make EXTRACT(EPOCH FROM timestamp without time zone) measure the
epoch from local midnight, not UTC midnight (Tom Lane)
On 09/24/2015 07:01 AM, Willy-Bas Loos wrote:
=# show timezone;
TimeZone
---
localtime
(1 row)
This sounded familiar:
http://www.postgresql.org/message-id/m3616t3m5d@carbon.jhcloos.org
From there, per Tom Lane:
select * from pg_settings where name = 'TimeZone';
This will s
On 09/24/2015 07:01 AM, Willy-Bas Loos wrote:
=# show timezone;
TimeZone
---
localtime
(1 row)
Is this the same on both 8.4 and 9.4?
Are both servers on the same machine?
What does /etc/localtime point to?
On Thu, Sep 24, 2015 at 3:57 PM, Adrian Klaver
mailto:adrian.kla...@ak
On Thu, Sep 24, 2015 at 4:01 PM, Willy-Bas Loos wrote:
> =# show timezone;
> TimeZone
> ---
> localtime
> (1 row)
>
>
>
sorry for the top post
--
Willy-Bas Loos
=# show timezone;
TimeZone
---
localtime
(1 row)
On Thu, Sep 24, 2015 at 3:57 PM, Adrian Klaver
wrote:
> On 09/24/2015 06:42 AM, Willy-Bas Loos wrote:
>
>> Hi,
>>
>> We're upgrading a database from 8.4 to 9.4
>> The web developer complains that the timestamps are suddenly 2 hours
>> l
On 09/24/2015 06:42 AM, Willy-Bas Loos wrote:
Hi,
We're upgrading a database from 8.4 to 9.4
The web developer complains that the timestamps are suddenly 2 hours
late. We are in GMT+02.
The issue would go away if we cast the postgres timestamps to timestamp
WITH timezone. It works in pg8.4 and 9
On 09/24/2015 03:42 PM, Willy-Bas Loos wrote:
> Hi,
>
> We're upgrading a database from 8.4 to 9.4
> The web developer complains that the timestamps are suddenly 2 hours late.
> We are in GMT+02.
> The issue would go away if we cast the postgres timestamps to timestamp
> WITH timezone. It works in
Hi,
We're upgrading a database from 8.4 to 9.4
The web developer complains that the timestamps are suddenly 2 hours late.
We are in GMT+02.
The issue would go away if we cast the postgres timestamps to timestamp
WITH timezone. It works in pg8.4 and 9.4
He told me that PHP always uses timezones, s
11 matches
Mail list logo