From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Edmundo Robles <edmundo(at)sw-argos(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: recovery dump on database with different timezone |
Date: | 2017-01-24 01:14:02 |
Message-ID: | CAKFQuwYa8+-UJGfeK0t-8eUt-8HPwJjZt91k3gbWvp+87bWadA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jan 23, 2017 at 6:08 PM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
>
> production=# show timezone;
> TimeZone
> ----------
> UTC
> (1 row)
>
> production=# select ' 2011-01-01 00:00:03.925-06'::timestamptz <
> '2011-01-01'::date;
> ?column?
> ----------
> f
>
What Tom said - though I missed the part about "the timezone when the data
was entered" - I was thinking it was only the timezone at the time of the
dump that would impact things.
To your example - testing in UTC is going to always result in failure for Z
values <= 0 since they will all result in a UTC date of 2011-01-01.
Choosing +06 would result in a passed test.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2017-01-24 01:23:44 | Re: recovery dump on database with different timezone |
Previous Message | Adrian Klaver | 2017-01-24 01:08:49 | Re: recovery dump on database with different timezone |