From 4c5e810fcda57940d1a7178389129591eb93d68e Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Fri, 1 Oct 2004 16:40:05 +0000 Subject: Code review for NOWAIT patch: downgrade NOWAIT from fully reserved keyword to unreserved keyword, use ereport not elog, assign a separate error code for 'could not obtain lock' so that applications will be able to detect that case cleanly. --- doc/src/sgml/errcodes.sgml | 7 ++++++- doc/src/sgml/ref/lock.sgml | 4 ++-- 2 files changed, 8 insertions(+), 3 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/errcodes.sgml b/doc/src/sgml/errcodes.sgml index 950f97151bc..7bcff2c1d90 100644 --- a/doc/src/sgml/errcodes.sgml +++ b/doc/src/sgml/errcodes.sgml @@ -1,4 +1,4 @@ - + <productname>PostgreSQL</productname> Error Codes @@ -1099,6 +1099,11 @@ CANT CHANGE RUNTIME PARAM + +55P03 +LOCK NOT AVAILABLE + + Class 57 diff --git a/doc/src/sgml/ref/lock.sgml b/doc/src/sgml/ref/lock.sgml index cab378ec95c..34e01c82a58 100644 --- a/doc/src/sgml/ref/lock.sgml +++ b/doc/src/sgml/ref/lock.sgml @@ -1,5 +1,5 @@ @@ -37,7 +37,7 @@ where lockmode is one of: if necessary for any conflicting locks to be released. If NOWAIT is specified, LOCK TABLE does not wait to acquire the desired lock: if it - cannot be immediately acquired, the transaction is aborted and an + cannot be acquired immediately, the command is aborted and an error is emitted. Once obtained, the lock is held for the remainder of the current transaction. (There is no UNLOCK TABLE command; locks are always released at transaction -- cgit v1.2.3