From: Tom Lane <tgl@sss.pgh.pa.us>
To: Laurenz Albe <laurenz.albe@cybertec.at>
cc: Adrian Klaver <adrian.klaver@aklaver.com>,
        Steve Crawford <scrawford@pinpointresearch.com>,
        PG-General Mailing List <pgsql-general@postgresql.org>
Subject: Re: Unexpected date conversion results
In-reply-to: <2e2a34695d84a297e62a2996466fecf97005a2fb.camel@cybertec.at>
References: <CAEfWYyzvM4XcfKunhvT1_xs_9rGnbXbRvnn_znQD4-Wg-aA5Vg@mail.gmail.com> <fd3ad9cc-50da-47a4-8177-3915ad7186bf@aklaver.com> <2e2a34695d84a297e62a2996466fecf97005a2fb.camel@cybertec.at>
Comments: In-reply-to Laurenz Albe <laurenz.albe@cybertec.at>
	message dated "Sat, 22 Nov 2025 01:43:19 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2555133.1763772908.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 21 Nov 2025 19:55:08 -0500
Message-ID: <2555134.1763772908@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/2555134.1763772908%40sss.pgh.pa.us>
Precedence: bulk

Laurenz Albe <laurenz.albe@cybertec.at> writes:
> I dug into the git history, and it has been like that since commit b3506=
006b564
> in 2002 (way before version 9.x).  That commit fixed a bug that returned=
 ten
> time the correct reault (but still offset from the UTC epoch).

I didn't bisect, but I get this in 9.1.24:

regression=3D# set timezone =3D 'America/Los_Angeles';
SET
regression=3D# select to_timestamp(extract(epoch from current_date));
      to_timestamp      =

------------------------
 2025-11-21 00:00:00-08
(1 row)

and this in 9.2.24:

regression=3D# set timezone =3D 'America/Los_Angeles';
SET
regression=3D# select to_timestamp(extract(epoch from current_date));
      to_timestamp      =

------------------------
 2025-11-20 16:00:00-08
(1 row)

			regards, tom lane