| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres' |
| Date: | 2024-12-12 23:36:39 |
| Message-ID: | 957591.1734046599@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-12-13 01:21:53 | Re: Build failure with GCC 15 (defaults to -std=gnu23) |
| Previous Message | Nathan Bossart | 2024-12-12 21:55:42 | Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails |