Re: Parallel safety of CURRENT_* family

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: 5bih4k+4jfl6m39j23k(at)guerrillamail(dot)com, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parallel safety of CURRENT_* family
Date: 2016-12-01 19:32:43
Message-ID: 9244.1480620763@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> <5bih4k+4jfl6m39j23k(at)guerrillamail(dot)com> writes:
>> pg_proc shows that now() is marked as restricted, but transaction_timestamp() is marked as safe.

> That's certainly silly, because they're equivalent. I should think
> they're both safe. Robert?

... well, they would be if we passed down xactStartTimestamp to parallel
workers, but I can't find any code that does that. In view of the fact that
transaction_timestamp() is marked as parallel-safe, this is a bug in 9.6.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2016-12-01 19:40:56 Re: Broken SSL tests in master
Previous Message Robert Haas 2016-12-01 19:22:19 Re: Broken SSL tests in master