Re: Possible old and fixed bug in Postgres? - Mailing list pgsql-general

From Tom Lane
Subject Re: Possible old and fixed bug in Postgres?
Date
Msg-id 1833663.1680704216@sss.pgh.pa.us
Whole thread Raw
In response to Re: Possible old and fixed bug in Postgres?  (Erik Wienhold <ewie@ewie.name>)
List pgsql-general
Erik Wienhold <ewie@ewie.name> writes:
>> On 05/04/2023 11:18 CEST Steve Rogerson <steve.git@woodsideendurance.co.uk> wrote:
>>     # 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
>> ...
>> 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

I think this was not fixed in full until 2008:

https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=0171e72d4da2da7974ff13c63130e2175cebee88

Either way, though, whatever Steve is looking at is far past its
sell-by date.

            regards, tom lane



pgsql-general by date:

Previous
From: Erik Wienhold
Date:
Subject: Re: Possible old and fixed bug in Postgres?
Next
From: Tom Lane
Date:
Subject: Re: PgOutput Replication Message Format - Differentiate between explicit NULL and Omitted Columns during Insert