On Wed, Feb 11, 2015 at 1:59 PM, Robert Haas <robertmh...@gmail.com> wrote: > I'm not sure what you mean by the "severity" of the lock. How about > marking the locks that the worker inherited from the parallel master > and throwing an error if it tries to lock one of those objects in a > mode that it does not already hold? That'd probably catch a sizeable > number of programming errors without tripping up many legitimate use > cases (and we can always relax or modify the prohibition if it later > turns out to be problematic).
Or maybe do that only when the new lock mode is stronger than one it already holds. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
