From: Robert Zenz <robert.zenz@sibvisions.com>
To: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: Strange behavior of the timezone
Date: Tue, 27 Mar 2018 09:46:32 +0000
Message-ID: <5ABA12F8.8040900@sibvisions.com> (raw)
In-Reply-To: <c3770e42-bf2c-7e5d-3bb0-a255fc8cf668@yandex.ru>
References: <CANYYVqL0M=-mVZH6T85jpO648pM5dVNu39n7i93M39JZmT=atQ@mail.gmail.com>
<c3770e42-bf2c-7e5d-3bb0-a255fc8cf668@yandex.ru>
That is not necessarily a strange behavior, as the Timezome most likely includes
all the adjustments that were made in the period of time (leap seconds and the
like). At least as far as I know.
How does it behave if you try a more current date, like today? What is your
system/database timezone?
On 27.03.2018 11:40, Vlad Alexeenkov wrote:
> Hi!
>
> Can anyone explain this behavior?
>
> select '1900-01-01 15:11:10'::timestamp t1, '1900-01-01 15:11:10'::timestamp at
> time zone 'Europe/Moscow' as t2
>
> t1 t2
> =================== ===================
> 01.01.1900 15:11:10 01.01.1900 15:40:53
>
> Strange behavior of the timezone
>
>
>
>
> select version()
>
> version
> ========================================================================================================
>
> PostgreSQL 9.6.5 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623
> (Red Hat 4.8.5-11), 64-bit
>
> Thanks
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: robert.zenz@sibvisions.com, pgsql-admin@lists.postgresql.org
Subject: Re: Strange behavior of the timezone
In-Reply-To: <5ABA12F8.8040900@sibvisions.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox