aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistxlog.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2005-09-09 06:51:12 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2005-09-09 06:51:12 +0000
commit35979e6c35b75b0f6ed68b60f120459380ead3c4 (patch)
tree443b451420c61a492f25989df481c86d048f5d93 /src/backend/access/gist/gistxlog.c
parentf2ebd01ef02968c03c3886296de3242bbc5f817d (diff)
downloadpostgresql-35979e6c35b75b0f6ed68b60f120459380ead3c4.tar.gz
postgresql-35979e6c35b75b0f6ed68b60f120459380ead3c4.zip
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.
Diffstat (limited to 'src/backend/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions