Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g8XiW-0007FC-FD for pgsql-hackers@arkaria.postgresql.org; Fri, 05 Oct 2018 21:33:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g8XiU-0005bn-LI for pgsql-hackers@arkaria.postgresql.org; Fri, 05 Oct 2018 21:32:58 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g8XiU-0005bg-EE for pgsql-hackers@lists.postgresql.org; Fri, 05 Oct 2018 21:32:58 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g8XiN-0007hu-Jg for pgsql-hackers@postgresql.org; Fri, 05 Oct 2018 21:32:57 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w95LWl7G005371; Fri, 5 Oct 2018 17:32:47 -0400 From: Tom Lane To: Konstantin Knizhnik cc: PostgreSQL Hackers , Robert Haas Subject: Re: now() vs transaction_timestamp() 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> Comments: In-reply-to Tom Lane message dated "Fri, 05 Oct 2018 17:25:25 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <5369.1538775167.1@sss.pgh.pa.us> Date: Fri, 05 Oct 2018 17:32:47 -0400 Message-ID: <5370.1538775167@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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