Re: pg_promote not marked as parallel-restricted in pg_proc.dat

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_promote not marked as parallel-restricted in pg_proc.dat
Date: 2018-10-29 08:41:08
Message-ID: 861d679f154e061b267d7c63a2509db691330d28.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexey Kondratov 2018-10-29 08:54:41 Re: [Patch] pg_rewind: options to use restore_command from recovery.conf or command line
Previous Message Masahiko Sawada 2018-10-29 08:37:52 Re: [HACKERS] Restricting maximum keep segments by repslots