| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org, Chris BSomething <xpusostomos(at)gmail(dot)com> |
| Subject: | Re: Inconsistency of timezones in postgresql |
| Date: | 2024-07-31 15:15:48 |
| Message-ID: | 3384710.1722438948@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Aleksander Alekseev <aleksander(at)timescale(dot)com> writes:
> Alternatively we could provide timezone_iso(text, timestamp[tz])
> functions that just replace all the +'s to -'s and vice versa in its
> first argument and then calls timezone().
That will add confusion, not reduce it.
> Thoughts?
I think this is a documentation issue, specifically that Section 8.5.3
is not sufficiently in-your-face about "UTC+2" not meaning what you
probably think. We didn't really do anybody any favors by shoving
those details off to Appendix B.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-07-31 15:16:03 | Re: Inconsistency of timezones in postgresql |
| Previous Message | Aleksander Alekseev | 2024-07-31 14:51:12 | Re: Inconsistency of timezones in postgresql |