pgsql: Fix parallel-safety markings for contrib/dblink.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix parallel-safety markings for contrib/dblink.
Date: 2016-06-18 03:08:27
Message-ID: E1bE6cV-0007HF-Oq@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/7e81a18d49f2ffc3397bde2660b255b56d8a6d77

Modified Files
--------------
contrib/dblink/dblink--1.1--1.2.sql | 6 +++---
contrib/dblink/dblink--1.2.sql | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Amit Kapila 2016-06-18 03:16:23 Re: pgsql: Try again to fix the way the scanjoin_target is used with partia
Previous Message Amit Kapila 2016-06-18 02:14:49 Re: pgsql: Try again to fix the way the scanjoin_target is used with partia