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

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Given its current definition that depends on time(NULL),
Date: 2005-09-09 06:51:14
Message-ID: 20050909065114.72740D80DF@svr1.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
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.

Modified Files:
--------------
pgsql/src/include/catalog:
pg_proc.h (r1.383 -> r1.384)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_proc.h.diff?r1=1.383&r2=1.384)

Browse pgsql-committers by date

  From Date Subject
Next Message User Dpage 2005-09-09 12:53:56 pginstaller - pginst: Updated Russian translation
Previous Message Tom Lane 2005-09-09 06:46:15 pgsql: timestamptz_izone should return the input, not NULL, when the