Postgres Pro
Downloads
Home   >   mailing lists

BUG #16553: now() function marked PARALLEL RESTRICTED whereas transaction_timestamp() is PARALLEL SAFE - Mailing list pgsql-bugs

From PG Bug reporting form
Subject BUG #16553: now() function marked PARALLEL RESTRICTED whereas transaction_timestamp() is PARALLEL SAFE
Date
Msg-id 16553-87ec344031c0b345@postgresql.org
Whole thread Raw
Responses Re: BUG #16553: now() function marked PARALLEL RESTRICTED whereas transaction_timestamp() is PARALLEL SAFE
List pgsql-bugs
Tree view 
The following bug has been logged on the website:

Bug reference:      16553
Logged by:          Giorgio Saviane
Email address:      gsaviane@gmail.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.

pgsql-bugs by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Buffers from parallel workers not accumulated to upper nodes with gather merge
Next
From: Michał Lis
Date:
Subject: Re: BUG #16550: Problem with pg_service.conf