pgsql: Mark binary_upgrade_set_missing_value as parallel_unsafe

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Mark binary_upgrade_set_missing_value as parallel_unsafe
Date: 2018-06-23 12:44:46
Message-ID: E1fWhuI-0001Pf-75@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Mark binary_upgrade_set_missing_value as parallel_unsafe

per buildfarm.

Bump catalog version again although in practice nobody is going to use
this in a parallel query.

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/123efbccea694626b36ad952086d883fa7469aa9

Modified Files
--------------
src/include/catalog/catversion.h | 2 +-
src/include/catalog/pg_proc.dat | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2018-06-23 20:35:29 pgsql: doc: mention use of cross platform logical replication
Previous Message Andrew Dunstan 2018-06-23 04:02:56 Re: pgsql: Allow for pg_upgrade of attributes with missing values