BUG #16553: now() function marked PARALLEL RESTRICTED whereas transaction_timestamp() is PARALLEL SAFE

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: gsaviane(at)gmail(dot)com
Subject: BUG #16553: now() function marked PARALLEL RESTRICTED whereas transaction_timestamp() is PARALLEL SAFE
Date: 2020-07-23 14:01:09
Message-ID: 16553-87ec344031c0b345@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 16553
Logged by: Giorgio Saviane
Email address: gsaviane(at)gmail(dot)com
PostgreSQL version: 11.8
Operating system: Linux
Description:

now() and transaction_timestamp() are described as being equivalent in the
guide
https://www.postgresql.org/docs/11/functions-datetime.html#FUNCTIONS-DATETIME-CURRENT.
However, using now() in a query can screw up a possible parallel plan since
it's labeled PARALLEL RESTRICTED.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michał Lis 2020-07-23 14:26:33 Re: BUG #16550: Problem with pg_service.conf
Previous Message Amit Kapila 2020-07-23 10:54:55 Re: Buffers from parallel workers not accumulated to upper nodes with gather merge