Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pk3wl-00089m-MA for pgsql-general@arkaria.postgresql.org; Wed, 05 Apr 2023 14:17:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pk3wi-0006rf-Rd for pgsql-general@arkaria.postgresql.org; Wed, 05 Apr 2023 14:17:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pk3wi-0006rV-Gu for pgsql-general@lists.postgresql.org; Wed, 05 Apr 2023 14:17:08 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pk3wb-0013nc-62 for pgsql-general@lists.postgresql.org; Wed, 05 Apr 2023 14:17:07 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 335EGu271833664; Wed, 5 Apr 2023 10:16:56 -0400 From: Tom Lane To: Erik Wienhold cc: Steve Rogerson , pgsql-general list Subject: Re: Possible old and fixed bug in Postgres? In-reply-to: <2134938884.639895.1680690198796@office.mailbox.org> References: <2134938884.639895.1680690198796@office.mailbox.org> Comments: In-reply-to Erik Wienhold message dated "Wed, 05 Apr 2023 12:23:18 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <1833662.1680704216.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 05 Apr 2023 10:16:56 -0400 Message-ID: <1833663.1680704216@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Erik Wienhold writes: >> On 05/04/2023 11:18 CEST Steve Rogerson wrote: >> =C2=A0=C2=A0=C2=A0 # For very early and late dates, PostgreSQL always r= eturns times in >> =C2=A0=C2=A0=C2=A0 # 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/fea= ture of = >> pg in the long ago. > Judging by the commit message and changed test cases, probably: > https://git.postgresql.org/gitweb/?p=3Dpostgresql.git;a=3Dcommit;h=3D921= d749bd4c34c3349f1c254d5faa2f1cec03911 I think this was not fixed in full until 2008: https://git.postgresql.org/gitweb/?p=3Dpostgresql.git&a=3Dcommitdiff&h=3D0= 171e72d4da2da7974ff13c63130e2175cebee88 Either way, though, whatever Steve is looking at is far past its sell-by date. regards, tom lane