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 20181029090349.GM14242@paquier.xyz
Whole thread Raw
In response to Re: pg_promote not marked as parallel-restricted in pg_proc.dat  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: pg_promote not marked as parallel-restricted in pg_proc.dat  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-hackers
On Mon, Oct 29, 2018 at 09:41:08AM +0100, Laurenz Albe wrote:
> I think that the question if pg_promote allows a parallel plan or not
> is mostly academic, but the two definitions should be kept in sync.

It seems to me that the presence of the trigger file written in $PGDATA
means that the function should be restricted.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] Transactions involving multiple postgres foreignservers, take 2
Next
From: Alexey Kondratov
Date:
Subject: Re: [Patch] pg_rewind: options to use restore_command fromrecovery.conf or command line