Mark pg_start_backup and pg_stop_backup as parallel-restricted.
authorRobert Haas <rhaas@postgresql.org>
Mon, 6 Mar 2017 17:41:55 +0000 (12:41 -0500)
committerRobert Haas <rhaas@postgresql.org>
Mon, 6 Mar 2017 17:41:55 +0000 (12:41 -0500)
commit9fe3c644a73198941e9a502958c24727dc4a6434
treefaa010631b3cf8d23ec595857b2751b29e2ade2c
parent7f6fa29f18aa84743185ee7ada97f277459228a7
Mark pg_start_backup and pg_stop_backup as parallel-restricted.

They depend on backend-private state that will not be synchronized by
the parallel machinery, so they should not be marked parallel-safe.
This issue also exists in 9.6, but we obviously can't do anything
about 9.6 clusters that already exist.  Possibly this could be
back-patched so that future 9.6 clusters would come out OK, or
possibly we should back-patch some other fix, but that would need more
discussion.

David Steele, reviewed by Michael Paquier

Discussion: http://postgr.es/m/CA+TgmoYCWfO2UM-t=HUMFJyxJywLDiLL0nAJpx88LKtvBvNECw@mail.gmail.com
src/include/catalog/catversion.h
src/include/catalog/pg_proc.h