pgsql: interval_out() must be marked STABLE, not IMMUTABLE. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: interval_out() must be marked STABLE, not IMMUTABLE.
Date
Msg-id E1nAJHJ-0006vd-J6@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
interval_out() must be marked STABLE, not IMMUTABLE.

Its results vary depending on the IntervalStyle GUC, so it cannot
be considered immutable.

This is an extremely ancient bug.  AFAICT it was a sloppy mistake
in 6f58115dd, which marked it "cacheable" alongside marking several
other interval functions that way.  At the time, interval_out()
depended on DateStyle not IntervalStyle, but it was still wrong.

Back-patching this change doesn't look very practical, so I won't.
Aside from the usual difficulties of getting catalog changes
applied to existing databases, people might have indexes,
generated columns, etc that depend on interval-to-text casts
being considered immutable.  (This'd not really give them any
problem as long as they never change IntervalStyle.)  They
wouldn't appreciate us breaking such usage in minor releases.

Per bug #17371 from Marcus Gartner.

Discussion: https://postgr.es/m/17371-8f57e6e9ca5e35bf@postgresql.org

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/a3d6264bbce0ff7002be35a907b73b01e2e37f45

Modified Files
--------------
src/include/catalog/catversion.h | 2 +-
src/include/catalog/pg_proc.dat  | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: TAP tests: check for postmaster.pid anyway when "pg_ctl start" f
Next
From: Jeff Davis
Date:
Subject: pgsql: Make logical decoding a part of the rmgr.