pgsql: Given its current definition that depends on time(NULL), - Mailing list pgsql-committers

From tgl@svr1.postgresql.org (Tom Lane)
Subject pgsql: Given its current definition that depends on time(NULL),
Date
Msg-id 20050909065114.72740D80DF@svr1.postgresql.org
Whole thread Raw
List 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)

pgsql-committers by date:

Previous
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql: timestamptz_izone should return the input, not NULL, when the
Next
From: dpage@pgfoundry.org (User Dpage)
Date:
Subject: pginstaller - pginst: Updated Russian translation