From 853cf6617629e7ffda4060266428bc9f78e14086 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Fri, 24 Mar 2000 01:20:09 +0000 Subject: [PATCH] Update HISTORY --- HISTORY | 4 ++-- doc/src/sgml/ref/lock.sgml | 12 ++++-------- doc/src/sgml/release.sgml | 4 ++-- 3 files changed, 8 insertions(+), 12 deletions(-) diff --git a/HISTORY b/HISTORY index e3155d25a8..5b50b9bcbc 100644 --- a/HISTORY +++ b/HISTORY @@ -161,7 +161,7 @@ Allow subselects on the left side of comparison operators (Tom) New parallel regression test (Jan) Change backend-side COPY to write files with permissions 644 not 666 (Tom) Force permissions on PGDATA directory to be secure, even if it exists (Tom) -Added psql LastOid variable to return last inserted oid (Peter E) +Added psql LASTOID variable to return last inserted oid (Peter E) Allow concurrent vacuum and remove pg_vlock vacuum lock file (Tom) Add permissions check so only Postgres superuser or table owner can vacuum (Peter E) @@ -182,7 +182,7 @@ Allow flag to control COPY input/output of NULLs (Peter E) Make postgres user have a password by default (Peter E) Add CREATE/ALTER/DROP GROUP (Peter E) All administration scripts now support --long options (Peter E, Karel) -Vacuumdb script now supports --alldb option (Peter E) +Vacuumdb script now supports --all option (Peter E) ecpg new portable FETCH syntax Add ecpg EXEC SQL IFDEF, EXEC SQL IFNDEF, EXEC SQL ELSE, EXEC SQL ELIF and EXEC SQL ENDIF directives diff --git a/doc/src/sgml/ref/lock.sgml b/doc/src/sgml/ref/lock.sgml index 051db61efd..6ff7b71810 100644 --- a/doc/src/sgml/ref/lock.sgml +++ b/doc/src/sgml/ref/lock.sgml @@ -1,5 +1,5 @@ @@ -87,8 +87,7 @@ LOCK [ TABLE ] name IN SHARE ROW EX If EXCLUSIVE or SHARE are not specified, EXCLUSIVE is assumed. - If ROW or ACCESS is not specified, the entire table is locked - for the duration of the transaction. + Locks exist for the duration of the transaction. @@ -117,14 +116,12 @@ LOCK [ TABLE ] name IN SHARE ROW EX This lock mode is acquired automatically over tables being queried. - It is released after the statement completes. - It does not remain for the duration of the transaction. This is the least restrictive lock mode. It conflicts only with - ACCESS EXCLUSIVE mode. It is used to protect a table being + ACCESS EXCLUSIVE mode. It is used to protect a table from being modified by concurrent ALTER TABLE, DROP TABLE and VACUUM commands. @@ -138,8 +135,7 @@ LOCK [ TABLE ] name IN SHARE ROW EX Automatically acquired by SELECT...FOR UPDATE. - While it is a shared lock, there is the intention to later upgrade - this to a ROW EXCLUSIVE lock. + While it is a shared lock, may be upgrade later to a ROW EXCLUSIVE lock. diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index 094b9befe9..7c1978982b 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -196,7 +196,7 @@ Allow subselects on the left side of comparison operators (Tom) New parallel regression test (Jan) Change backend-side COPY to write files with permissions 644 not 666 (Tom) Force permissions on PGDATA directory to be secure, even if it exists (Tom) -Added psql LastOid variable to return last inserted oid (Peter E) +Added psql LASTOID variable to return last inserted oid (Peter E) Allow concurrent vacuum and remove pg_vlock vacuum lock file (Tom) Add permissions check so only Postgres superuser or table owner can vacuum (Peter E) @@ -217,7 +217,7 @@ Allow flag to control COPY input/output of NULLs (Peter E) Make postgres user have a password by default (Peter E) Add CREATE/ALTER/DROP GROUP (Peter E) All administration scripts now support --long options (Peter E, Karel) -Vacuumdb script now supports --alldb option (Peter E) +Vacuumdb script now supports --all option (Peter E) ecpg new portable FETCH syntax Add ecpg EXEC SQL IFDEF, EXEC SQL IFNDEF, EXEC SQL ELSE, EXEC SQL ELIF and EXEC SQL ENDIF directives