Re: Parallel safety of CURRENT_* family

I wrote:
> <5bih4k+4jfl6m39j23k@guerrillamail.com> writes:
>> pg_proc shows that now() is marked as restricted, but transaction_timestamp() is marked as safe.

> That's certainly silly, because they're equivalent.  I should think
> they're both safe.  Robert?

... well, they would be if we passed down xactStartTimestamp to parallel
workers, but I can't find any code that does that.  In view of the fact that
transaction_timestamp() is marked as parallel-safe, this is a bug in 9.6.
        regards, tom lane