pgsql: Mark advisory-lock functions as parallel restricted, not paralle

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Mark advisory-lock functions as parallel restricted, not paralle
Date: 2019-08-01 15:50:12
Message-ID: E1htDLI-00088E-Tj@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/4886da8327507dddd830786b0c7aaa9cfc480b4b

Modified Files
--------------
src/include/catalog/catversion.h | 2 +-
src/include/catalog/pg_proc.dat | 42 ++++++++++++++++++++--------------------
2 files changed, 22 insertions(+), 22 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Shay Rojansky 2019-08-01 16:33:52 Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.)
Previous Message Tom Lane 2019-08-01 14:08:01 Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.)