pgsql: Fix parallel-safety markings for pg_upgrade functions.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix parallel-safety markings for pg_upgrade functions.
Date: 2016-02-07 16:46:17
Message-ID: E1aSSTZ-00085O-Dv@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix parallel-safety markings for pg_upgrade functions.

These establish backend-local state which will not be copied to
parallel workers, so they must be marked parallel-restricted, not
parallel-safe.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/d89f06f0482458d4b76e3be67ea428fec2a0aeb6

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

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2016-02-07 17:19:21 Re: pgsql: Add gin_clean_pending_list function to clean up GIN pending list
Previous Message Robert Haas 2016-02-07 16:42:03 pgsql: Introduce a new GUC force_parallel_mode for testing purposes.