From: | Robert Haas <rhaas(at)postgresql(dot)org> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Fix parallel safety markings for pg_start_backup. |
Date: | 2016-05-02 14:44:23 |
Message-ID: | E1axF5D-0005ei-34@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Fix parallel safety markings for pg_start_backup.
Commit 7117685461af50f50c03f43e6a622284c8d54694 made pg_start_backup
parallel-restricted rather than parallel-safe, because it now relies
on backend-private state that won't be synchronized with the parallel
worker. However, it didn't update pg_proc.h. Separately, Andreas
Karlsson observed that system_views.sql neglected to reiterate the
parallel-safety markings whe redefining various functions, including
this one; so add a PARALLEL RESTRICTED declaration there to match
the new value in pg_proc.h.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/37d0c2cb1ab2d3da0cb9a6388450776fc31c16ee
Modified Files
--------------
src/backend/catalog/system_views.sql | 3 ++-
src/include/catalog/catversion.h | 2 +-
src/include/catalog/pg_proc.h | 2 +-
3 files changed, 4 insertions(+), 3 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2016-05-02 14:47:28 | Re: pgsql: Fix parallel safety markings for pg_start_backup. |
Previous Message | Robert Haas | 2016-05-02 14:32:28 | Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold < |