Re: now() vs transaction_timestamp()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: now() vs transaction_timestamp()
Date: 2018-10-05 13:56:35
Message-ID: 4268.1538747795@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Laurenz Albe 2018-10-05 14:34:34 Re: Libpq support to connect to standby server as priority
Previous Message Andrew Dunstan 2018-10-05 13:31:18 Re: Relax transactional restrictions on ALTER ENUM ... ADD TYPE (redux)