Re: now() vs transaction_timestamp()

Konstantin Knizhnik <k.knizhnik@postgrespro.ru> writes:
> Postgres documentation says that |"now()| is a traditional PostgreSQL 
> equivalent to |transaction_timestamp()|".
> Also both use the same implementation.

Right.

> But them have different parallel safety property:

That seems like a bug/thinko.  I am not sure which property setting is
correct though.  It'd only be safe if the parallel-query infrastructure
transfers the relevant timestamp to workers, and I don't know if it does.

            regards, tom lane