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

From Laurenz Albe
Subject Re: pg_promote not marked as parallel-restricted in pg_proc.dat
Date
Msg-id 861d679f154e061b267d7c63a2509db691330d28.camel@cybertec.at
Whole thread Raw
In response to 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  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Michael Paquier wrote:
> It looks that I forgot to mark pg_promote as parallel-restricted in
> 1007465 in pg_proc.dat.  It seems to me that this is not a huge issue as
> system_views.sql redefines the function for its default values and
> enforces parallel-restricted, but let's be right from the start.
> 
> Attached is a patch to fix that.  Any comments or objections?

Hmm, I should have noticed that.

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.

Yours,
Laurenz Albe



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] Restricting maximum keep segments by repslots
Next
From: Alexey Kondratov
Date:
Subject: Re: [Patch] pg_rewind: options to use restore_command fromrecovery.conf or command line