From 5e84d58e701e3feea1b08b1d66525a06824e7224 Mon Sep 17 00:00:00 2001 From: "Thomas G. Lockhart" Date: Mon, 14 Jun 1999 07:36:12 +0000 Subject: [PATCH] Minor updates for release. --- doc/src/sgml/datatype.sgml | 2 +- doc/src/sgml/docguide.sgml | 7 +- doc/src/sgml/func.sgml | 1362 ++++++++++++++++++------------------ doc/src/sgml/lobj.sgml | 285 ++++---- doc/src/sgml/release.sgml | 14 +- 5 files changed, 851 insertions(+), 819 deletions(-) diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index 16a0074010..8425bb4fa6 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -1,5 +1,5 @@ - Data Types + Data Types diff --git a/doc/src/sgml/docguide.sgml b/doc/src/sgml/docguide.sgml index d16e3c1d1a..af4e7b0464 100644 --- a/doc/src/sgml/docguide.sgml +++ b/doc/src/sgml/docguide.sgml @@ -1,9 +1,12 @@ diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index 1d3f2c661e..c6ccb00402 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -23,7 +23,7 @@ - Here is a brief summary of some of the more noticable changes: + Here is a brief summary of the more notable changes: @@ -188,16 +188,16 @@ Because readers in 6.5 don't lock data, regardless of transaction isolation level, data read by one transaction can be overwritten by - another. In the other words, if a row is returned by + another. In other words, if a row is returned by SELECT it doesn't mean that this row really exists at the time it is returned (i.e. sometime after the statement or - transaction began) nor that the row is protected from deletion or - update by concurrent transactions before the current transaction does + transaction began) nor that the row is protected from being deleted or + updated by concurrent transactions before the current transaction does a commit or rollback. - To ensure the actual existance of a row and protect it against + To ensure the actual existence of a row and protect it against concurrent updates one must use SELECT FOR UPDATE or an appropriate LOCK TABLE statement. This should be taken into account when porting applications from previous releases of @@ -205,7 +205,8 @@ - Keep above in mind if you are using contrib/refint.* triggers for + Keep the above in mind if you are using + contrib/refint.* triggers for referential integrity. Additional technics are required now. One way is to use LOCK parent_table IN SHARE ROW EXCLUSIVE MODE command if a transaction is going to update/delete a primary key and @@ -2634,6 +2635,7 @@ Initial release. Time System 02:00 Dual Pentium Pro 180, 224MB, UW-SCSI, Linux 2.0.36, gcc 2.7.2.3 -O2 -m486 + 04:38 Sparc Ultra 1 143MHz, 64MB, Solaris 2.6 -- GitLab