Given its current definition that depends on time(NULL), timetz_zone

is certainly no longer immutable, but must indeed be marked volatile.
I wonder if it should use the value of now() (that is, transaction
start time) so that it could be marked stable.  But it's probably not
important enough to be worth changing the code for ... indeed, I'm not
even going to force an initdb for this catalog change, seeing that we
just did one a few hours ago.

diff --git a/src/include/catalog/pg_proc.h b/src/include/catalog/pg_proc.h
index 485205cd5d13fa3dc2a802084c06a483a9dada25..44468d139df44cfb856221b19690865a2bd20d43 100644 (file)
--- a/src/include/catalog/pg_proc.h
+++ b/src/include/catalog/pg_proc.h
@@ -2959,7 +2959,7 @@ DATA(insert OID = 2035 (  timestamp_smaller PGNSP PGUID 12 f f t f i 2 1114 "111
 DESCR("smaller of two");
 DATA(insert OID = 2036 (  timestamp_larger     PGNSP PGUID 12 f f t f i 2 1114 "1114 1114" _null_ _null_ _null_        timestamp_larger - _null_ ));
 DESCR("larger of two");
-DATA(insert OID = 2037 (  timezone                     PGNSP PGUID 12 f f t f i 2 1266 "25 1266" _null_ _null_ _null_  timetz_zone - _null_ ));
+DATA(insert OID = 2037 (  timezone                     PGNSP PGUID 12 f f t f v 2 1266 "25 1266" _null_ _null_ _null_  timetz_zone - _null_ ));
 DESCR("adjust time with time zone to new zone");
 DATA(insert OID = 2038 (  timezone                     PGNSP PGUID 12 f f t f i 2 1266 "1186 1266" _null_ _null_ _null_        timetz_izone - _null_ ));
 DESCR("adjust time with time zone to new zone");