Re: Patch: shouldn't timezone(text, timestamp[tz]) be STABLE?
Aleksander Alekseev <aleksander@timescale.com>
From: Aleksander Alekseev <aleksander@timescale.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-08-30T16:09:14Z
Lists: pgsql-hackers
Hi Tom, Thanks for the quick reply. > I don't see a lot of argument for treating tzdata changes differently > from OS locale changes. Got it. But in this case, what's your opinion on the differences between date_trunc() and timezone()? Shouldn't date_trunc() be always IMMUTABLE as well? I can see pros and cons to be IMMUTABLE _or_ STABLE when dealing with time zones, but at least PostgreSQL should be consistent in this, right? -- Best regards, Aleksander Alekseev
Commits
-
Fix actively-misleading comments about the contents of struct pg_tm.
- 89dba59590fd 15.0 landed
-
Fix bogus timetz_zone() results for DYNTZ abbreviations.
- eb3c8d24808a 12.9 landed
- d8a266c5e1bd 13.5 landed
- b28c862a6c11 10.19 landed
- 90b4647f63da 11.14 landed
- 599c73a91a04 14.0 landed
- 5907c3818c43 9.6.24 landed
-
Make timetz_zone() stable, and correct a bug for DYNTZ abbreviations.
- 388e71af880d 15.0 landed