From 9b4cda0df674e0c7b70aa61d768471a97205113f Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 18 Sep 2006 22:40:40 +0000 Subject: Add built-in userlock manipulation functions to replace the former contrib functionality. Along the way, remove the USER_LOCKS configuration symbol, since it no longer makes any sense to try to compile that out. No user documentation yet ... mmoncure has promised to write some. Thanks to Abhijit Menon-Sen for creating a first draft to work from. --- doc/src/sgml/catalogs.sgml | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index 2201a687eb7..bc5592ce746 100644 --- a/doc/src/sgml/catalogs.sgml +++ b/doc/src/sgml/catalogs.sgml @@ -1,4 +1,4 @@ - + @@ -5029,9 +5029,14 @@ - If user-defined locks are in use, they are displayed using the columns - for general database objects. However, the actual meaning of the lock - fields in such cases is up to the user. + User-defined locks can be acquired on keys consisting of either a single + bigint value or two integer values. A bigint key is displayed with its + high-order half in the classid column, its low-order half + in the objid column, and objsubid equal + to 1. Integer keys are displayed with the first key in the + classid column, the second key in the objid + column, and objsubid equal to 2. The actual meaning of + the keys is up to the user. -- cgit v1.2.3