Thomas Lockhart <lockhart@fourpalms.org> writes:
> On a modestly related note, I'm come over to the notion that the
> date/time value 'current' could be ripped out eventually. Tom, isn't
> that the only case for those types which bolluxes up caching of
> date/time types?
Yes, I believe so. At least, that was the consideration that led me
to mark those functions noncachable ...
regards, tom lane