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>
Cc: 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 09:09:38
Message-ID: 26756b63fc9662fc3d54e762460c8c1562d7c14a.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Paquier wrote:
> 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.

Yes, it should be PARALLEL RESTRICTED or PARALLEL UNSAFE, but it won't matter
much in practice which of the two we choose.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2018-10-29 09:10:56 Re: New vacuum option to do only freezing
Previous Message Alexey Kondratov 2018-10-29 09:09:21 Re: [Patch] pg_rewind: options to use restore_command from recovery.conf or command line