Re: pgsql: Fix parallel-safety markings for contrib/dblink. - Mailing list pgsql-committers

From Robert Haas
Subject Re: pgsql: Fix parallel-safety markings for contrib/dblink.
Date
Msg-id CA+TgmoaAgURV2Ck3T5W-ffuHc1+tk1G=h_DHsqWhbDXhqu77Ww@mail.gmail.com
Whole thread Raw
In response to pgsql: Fix parallel-safety markings for contrib/dblink.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On Fri, Jun 17, 2016 at 11:08 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Fix parallel-safety markings for contrib/dblink.
>
> As shown by buildfarm reports, dblink_build_sql_insert and
> dblink_build_sql_update are *not* parallel safe, because they
> may attempt to access temporary tables of the local session.
>
> Although dblink_build_sql_delete doesn't actually touch the
> contents of the referenced table, it seems consistent and prudent
> to mark it PARALLEL RESTRICTED too.

Ugh, thanks.  I thought that's how they WERE marked, but evidently my
eyes were crossing by this point.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Try again to fix the way the scanjoin_target is used with partia
Next
From: Amit Kapila
Date:
Subject: Re: pgsql: Try again to fix the way the scanjoin_target is used with partia