From: | Steve Rogerson <steve(dot)git(at)woodsideendurance(dot)co(dot)uk> |
---|---|
To: | pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Possible old and fixed bug in Postgres? |
Date: | 2023-04-05 09:18:43 |
Message-ID: | f8a40a55-0cfe-9c48-1f34-c157f34b5f46@woodsideendurance.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
Steve
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Wienhold | 2023-04-05 10:23:18 | Re: Possible old and fixed bug in Postgres? |
Previous Message | Pranav Hegde | 2023-04-05 09:09:28 | PgOutput Replication Message Format - Differentiate between explicit NULL and Omitted Columns during Insert |