From: Tom Lane <tgl@sss.pgh.pa.us>
To: Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Cc: Robert Haas <robertmhaas@gmail.com>
Subject: Re: now() vs transaction_timestamp()
Date: Fri, 05 Oct 2018 17:32:47 -0400
Message-ID: <5370.1538775167@sss.pgh.pa.us> (raw)
In-Reply-To: <4911.1538774725@sss.pgh.pa.us>
References: <6406dbd2-5d37-4cb6-6eb2-9c44172c7e7c@postgrespro.ru>
<4268.1538747795@sss.pgh.pa.us>
<4911.1538774725@sss.pgh.pa.us>
I wrote:
> So transaction_timestamp() is definitely buggy, but we're not out of the
> woods yet: SQLValueFunction is treated as parallel-safe, but it also has
> some instances that are equivalent to transaction_timestamp and so do not
> work correctly.
Oh, and I notice that timestamp_in and related functions are marked
parallel safe, which is equally broken since the conversion of 'now'
also depends on xactStartTimestamp.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, k.knizhnik@postgrespro.ru, robertmhaas@gmail.com
Subject: Re: now() vs transaction_timestamp()
In-Reply-To: <5370.1538775167@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox