summaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistget.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2019-08-01 11:36:21 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2019-08-01 11:36:21 -0400
commit4886da8327507dddd830786b0c7aaa9cfc480b4b (patch)
treed75554e39a30060fe7beb02557700079235d406e /src/backend/access/gist/gistget.c
parentfd6ec93bf890314ac694dc8a7f3c45702ecc1bbd (diff)
downloadpostgresql-4886da8327507dddd830786b0c7aaa9cfc480b4b.tar.gz
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
Diffstat (limited to 'src/backend/access/gist/gistget.c')
0 files changed, 0 insertions, 0 deletions