Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1tLsjf-00085z-GB
	for pgsql-bugs@arkaria.postgresql.org; Thu, 12 Dec 2024 23:36:47 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1tLsjc-00FFjI-3G
	for pgsql-bugs@arkaria.postgresql.org; Thu, 12 Dec 2024 23:36:45 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1tLsjb-00FFj7-Qv
	for pgsql-bugs@lists.postgresql.org; Thu, 12 Dec 2024 23:36:45 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by magus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1tLsjZ-002XvK-Nn
	for pgsql-bugs@lists.postgresql.org; Thu, 12 Dec 2024 23:36:44 +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 4BCNadgo957592;
	Thu, 12 Dec 2024 18:36:39 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Laurenz Albe <laurenz.albe@cybertec.at>
cc: Aleksander Alekseev <aleksander@timescale.com>,
        Michael Paquier <michael@paquier.xyz>, pgsql-bugs@lists.postgresql.org
Subject: Re: TimestampTz->Text->TimestampTz casting fails with DateStyle
 'Postgres'
In-reply-to: <2119430fb8604d819f55d6b65eeebf257e5d90a9.camel@cybertec.at>
References: 
 <CAJ7c6TOATjJqvhnYsui0=CO5XFMF4dvTGH+skzB--jNhqSQu5g@mail.gmail.com>
 <3416600.1730987836@sss.pgh.pa.us>
 <CAJ7c6TMzJDLutYt+pcm1Jt+sDSRHjvjezM9o8heEoo_LwgP75A@mail.gmail.com>
 <CAJ7c6TMpBUMLqep4ycxySN+SFsf-eG2v-nUaVSzu2jSd5eDMAA@mail.gmail.com>
 <Z1eKmoJHXVd8_oz1@paquier.xyz> <4167039.1733796752@sss.pgh.pa.us>
 <394372.1733884998@sss.pgh.pa.us> <521765.1733949428@sss.pgh.pa.us>
 <536069.1733956838@sss.pgh.pa.us>
 <2119430fb8604d819f55d6b65eeebf257e5d90a9.camel@cybertec.at>
Comments: In-reply-to Laurenz Albe <laurenz.albe@cybertec.at>
	message dated "Thu, 12 Dec 2024 07:40:31 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <957590.1734046599.1@sss.pgh.pa.us>
Date: Thu, 12 Dec 2024 18:36:39 -0500
Message-ID: <957591.1734046599@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/957591.1734046599%40sss.pgh.pa.us>
Precedence: bulk

Laurenz Albe <laurenz.albe@cybertec.at> writes:
> I agree that something should be done, but I'd have no problem
> with deprecating the Postgres datestyle.  People who depend on
> it can switch to using to_date() and to_timestamp(), which
> shouldn't impose too much hardship if we give them enough time.

It's not like to_timestamp doesn't have the same problem...

Anyway, I've started a -hackers thread about this issue at [1].
Whatever we do probably deserves wider discussion than it will
get on pgsql-bugs.

			regards, tom lane

[1] https://www.postgresql.org/message-id/957280.1734046384%40sss.pgh.pa.us