pgsql: Fix volatility marking of timestamptz_trunc_zone.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix volatility marking of timestamptz_trunc_zone.
Date: 2022-11-12 18:30:09
Message-ID: E1otvGa-000now-Sy@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/533e02e927c6e7fcc1a7b3121093d8f05b728279

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

Browse pgsql-committers by date

  From Date Subject
Next Message Noah Misch 2022-11-12 19:24:05 pgsql: If wait_for_catchup fails under has_wal_read_bug, skip balance o
Previous Message Jeff Davis 2022-11-12 16:44:35 pgsql: Document WAL rules related to PD_ALL_VISIBLE in README.