Re: now() vs transaction_timestamp() - Mailing list pgsql-hackers

From Tom Lane
Subject Re: now() vs transaction_timestamp()
Date
Msg-id 4268.1538747795@sss.pgh.pa.us
Whole thread Raw
In response to now() vs transaction_timestamp()  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
Responses Re: now() vs transaction_timestamp()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Relax transactional restrictions on ALTER ENUM ... ADD TYPE(redux)
Next
From: Laurenz Albe
Date:
Subject: Re: Libpq support to connect to standby server as priority