Re: Parallel safety of CURRENT_* family - Mailing list pgsql-hackers

<5bih4k+4jfl6m39j23k@guerrillamail.com> writes:
> How should I mark a function which calls CURRENT_DATE? Parallel safe or parallel restricted?

> 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?
        regards, tom lane