]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Mark advisory-lock functions as parallel restricted, not parallel unsafe.
authorTom Lane <tgl@sss.pgh.pa.us>
Thu, 1 Aug 2019 15:36:21 +0000 (11:36 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Thu, 1 Aug 2019 15:36:21 +0000 (11:36 -0400)
commit4886da8327507dddd830786b0c7aaa9cfc480b4b
treed75554e39a30060fe7beb02557700079235d406e
parentfd6ec93bf890314ac694dc8a7f3c45702ecc1bbd
Mark advisory-lock functions as parallel restricted, not parallel unsafe.

There seems no good reason not to allow a parallel leader to execute
these functions.  (The workers still can't, though.  Although the code
would work, any such lock would go away at worker exit, which is not
the documented behavior of advisory locks.)

Discussion: https://postgr.es/m/11847.1564496844@sss.pgh.pa.us
src/include/catalog/catversion.h
src/include/catalog/pg_proc.dat