Re: pg_promote not marked as parallel-restricted in pg_proc.dat - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: pg_promote not marked as parallel-restricted in pg_proc.dat
Date
Msg-id 20181102230236.GB1899@paquier.xyz
Whole thread Raw
In response to Re: pg_promote not marked as parallel-restricted in pg_proc.dat  (Michael Paquier <michael@paquier.xyz>)
Responses Re: pg_promote not marked as parallel-restricted in pg_proc.dat
List pgsql-hackers
On Fri, Nov 02, 2018 at 09:27:39AM +0900, Michael Paquier wrote:
> You actually do a lot, moving just one person with MP as initials to
> consider moving the function as being parallel-safe.  Thanks for the
> points you raised, what needs to be done looks clear now.

So anybody has an objection with marking the function as parallel-safe?
I'd like to do so if that's not the case and close the case.

What has been raised on this thread is more than I hoped first.  Thanks
Amit and Robert for the additional input!
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: partitioned indexes and tablespaces
Next
From: Alvaro Herrera
Date:
Subject: Re: partitioned indexes and tablespaces