Re: Possible old and fixed bug in Postgres?

From: Erik Wienhold <ewie(at)ewie(dot)name>
To: Steve Rogerson <steve(dot)git(at)woodsideendurance(dot)co(dot)uk>, pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Possible old and fixed bug in Postgres?
Date: 2023-04-05 10:23:18
Message-ID: 2134938884.639895.1680690198796@office.mailbox.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> On 05/04/2023 11:18 CEST Steve Rogerson <steve(dot)git(at)woodsideendurance(dot)co(dot)uk> wrote:
>
> I was looking at perl CPAN Module (DateTime::Format::Pg) and saw that it did
> something that seemed odd to me with time zones, based on the comment:
>
>     # For very early and late dates, PostgreSQL always returns times in
>     # UTC and does not tell us that it did so.
>
> Early is before 1901-12-14 and late after 2038-01-18
>
> A quick test setting my time zone to be America/Chicago I got
>
> select '1900-01-01 00:00:00'::timestamptz;
>       timestamptz
> ------------------------
>  1900-01-01 00:00:00-06
> (1 row)
>
> and
>
> select '2040-01-01 00:00:00'::timestamptz;
>       timestamptz
> ------------------------
>  2040-01-01 00:00:00-06
>
>
> These seemed correct to me. I'm guessing this might have been a bug/feature of
> pg in the long ago.

Judging by the commit message and changed test cases, probably:

https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=921d749bd4c34c3349f1c254d5faa2f1cec03911

--
Erik

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2023-04-05 14:16:56 Re: Possible old and fixed bug in Postgres?
Previous Message Steve Rogerson 2023-04-05 09:18:43 Possible old and fixed bug in Postgres?