Re: Date/Time parsing of ISO 8601 timestamps with commas

That linked thread covers the topic quite well. I didn't find it because the search function on the website only goes back 1 year.

I think adding some note to the documentation would be appropriate.

________________________________
From: David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
Sent: Saturday, October 11, 2025 7:30:01 AM
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Zane Duffield <duffieldzane(at)gmail(dot)com>; pgsql-bugs(at)lists(dot)postgresql(dot)org <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Date/Time parsing of ISO 8601 timestamps with commas

On Fri, Oct 10, 2025 at 4:09 PM Nathan Bossart <nathandbossart(at)gmail(dot)com<mailto:nathandbossart(at)gmail(dot)com>> wrote:
On Fri, Oct 10, 2025 at 10:43:04AM +1100, Zane Duffield wrote:
> I noticed today that PostgreSQL doesn't support parsing ISO 8601 timestamps
> that use a comma as the decimal separator.

I found various threads about this in the archives, including this one:

https://postgr.es/m/flat/152271186941.1442.12179299369295226185%40wrigleys.postgresql.org

If there are indeed various threads we might want to update the documentation to make it clear that we say "almost" because we don't correctly interpret formats that have substituted a comma for a full-stop. (And maybe other exceptions.)

Or, I suppose, Appendix B.1 step 1 should include a 5th note (or maybe add a step 0): "If the token is a comma it is replaced by a space".

David J.