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=humfjyxjywldill0najpx88lktvbvn...@mail.gmail.com Branch ------ master Details ------- http://git.postgresql.org/pg/commitdiff/9fe3c644a73198941e9a502958c24727dc4a6434 Modified Files -------------- src/include/catalog/catversion.h | 2 +- src/include/catalog/pg_proc.h | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
