Fix volatility marking of timestamptz_trunc_zone.
authorTom Lane <tgl@sss.pgh.pa.us>
Sat, 12 Nov 2022 18:29:41 +0000 (13:29 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Sat, 12 Nov 2022 18:29:52 +0000 (13:29 -0500)
commit533e02e927c6e7fcc1a7b3121093d8f05b728279
treefe7949cb2e26b3cf16bba7a79a6f2b371a5463c1
parent97c61f70d1b97bdfd20dcb1f2b1be42862ec88c2
Fix volatility marking of timestamptz_trunc_zone.

It's safe to mark this as immutable, because it does not depend
on the timezone GUC setting.  Oversight in commit 600b04d6b.

(There's an argument that timezone definitions do change from
time to time, but we have not worried about that in marking
other timestamp-related functions; for example AT TIME ZONE
has always been considered immutable.  The situation is no
worse than our problems with time-varying locales, surely.)

Przemysław Sztoch

Discussion: https://postgr.es/m/eaa3fabe-50fc-bbe8-b096-ce62ddadab85@sztoch.pl
src/include/catalog/catversion.h
src/include/catalog/pg_proc.dat