1berry/MariaDB-server
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fixed typo.

Browse Source 
Added update about PostgreSQL 7.2 and VACUUM.
This commit is contained in:
arjen@co3064164-a.bitbike.com 2002-02-18 12:21:47 +10:00
parent aa470adf5b
commit 531ae581fb
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Docs/manual.texi
View File

@ -4823,8 +4823,10 @@ adding a lot of new rows to a table. On a busy system with lots of changes,
@code{VACUUM()} must be run very frequently, in the worst cases even
many times a day. During the @code{VACUUM()} run, which may take hours
if the database is big, the database is from a production standpoint,
practically dead. The PostgreSQL team has fixing this on their TODO,
but we assume that this is not an easy thing to fix permanently.
practically dead. Please note: In PostgreSQL version 7.2, basic vacuuming
no longer locks tables, thus allowing normal user access during the vacuum.
A new @code{VACUUM FULL} command does old-style vacuum by locking the table
and shrinking the on-disk copy of the table.
@item
MySQL replication has been thoroughly tested, and is used by sites like:
@ -22751,7 +22753,7 @@ shell> perror [OPTIONS] [ERRORCODE [ERRORCODE...]]
Example:
shell> perror 13 64
Error code 13: Permission decided
Error code 13: Permission denied
Error code 64: Machine is not on the network
@end example