diff options
| author | Bruce Momjian <bruce@momjian.us> | 2007-01-31 20:56:20 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2007-01-31 20:56:20 +0000 |
| commit | a134ee33794d7066143f5587d9c36bcca62bfc39 (patch) | |
| tree | 86772780b602023fbc8f9d7e50fb9d5fa5bd7c3f /doc/src/sgml/diskusage.sgml | |
| parent | 67a1ae9f05f9311768ba0a4819f6b09d449c4294 (diff) | |
| download | postgresql-a134ee33794d7066143f5587d9c36bcca62bfc39.tar.gz | |
Update documentation on may/can/might:
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
Also update two error messages mentioned in the documenation to match.
Diffstat (limited to 'doc/src/sgml/diskusage.sgml')
| -rw-r--r-- | doc/src/sgml/diskusage.sgml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/src/sgml/diskusage.sgml b/doc/src/sgml/diskusage.sgml index f1cab2a677..1399fad570 100644 --- a/doc/src/sgml/diskusage.sgml +++ b/doc/src/sgml/diskusage.sgml @@ -1,4 +1,4 @@ -<!-- $PostgreSQL: pgsql/doc/src/sgml/diskusage.sgml,v 1.17 2006/09/16 00:30:12 momjian Exp $ --> +<!-- $PostgreSQL: pgsql/doc/src/sgml/diskusage.sgml,v 1.18 2007/01/31 20:56:16 momjian Exp $ --> <chapter id="diskusage"> <title>Monitoring Disk Usage</title> @@ -21,7 +21,7 @@ there is also a <acronym>TOAST</> file associated with the table, which is used to store values too wide to fit comfortably in the main table (see <xref linkend="storage-toast">). There will be one index on the - <acronym>TOAST</> table, if present. There may also be indexes associated + <acronym>TOAST</> table, if present. There might also be indexes associated with the base table. Each table and index is stored in a separate disk file — possibly more than one file, if the file would exceed one gigabyte. Naming conventions for these files are described in <xref @@ -117,9 +117,9 @@ SELECT relname, relpages FROM pg_class ORDER BY relpages DESC; <para> The most important disk monitoring task of a database administrator is to make sure the disk doesn't grow full. A filled data disk will - not result in data corruption, but it may well prevent useful activity + not result in data corruption, but it might prevent useful activity from occurring. If the disk holding the WAL files grows full, database - server panic and consequent shutdown may occur. + server panic and consequent shutdown might occur. </para> <para> |