From e81c138e18b54e272d917e5e8c4c8ae1b89cd133 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Wed, 31 Jan 2007 23:26:05 +0000 Subject: Update reference 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". --- doc/src/sgml/ref/postgres-ref.sgml | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) (limited to 'doc/src/sgml/ref/postgres-ref.sgml') diff --git a/doc/src/sgml/ref/postgres-ref.sgml b/doc/src/sgml/ref/postgres-ref.sgml index 9088c87ec9f..285da158b5d 100644 --- a/doc/src/sgml/ref/postgres-ref.sgml +++ b/doc/src/sgml/ref/postgres-ref.sgml @@ -1,5 +1,5 @@ @@ -354,13 +354,13 @@ PostgreSQL documentation Semi-internal Options - There are several other options that may be specified, used + There are several other options that can be specified, used mainly for debugging purposes and in some cases to assist with recovery of severely damaged databases. There should be no reason to use them in a production database setup. These are listed here only for the use by PostgreSQL - system developers. Furthermore, any of these options may - disappear or change in a future release without notice. + system developers. Furthermore, these options might + change or be removed in a future release without notice. @@ -559,7 +559,7 @@ PostgreSQL documentation - Default character encoding used by clients. (The clients may + Default character encoding used by clients. (The clients can override this individually.) This value can also be set in the configuration file. @@ -617,7 +617,7 @@ PostgreSQL documentation A failure message mentioning semget or shmget probably indicates you need to configure your kernel to provide adequate shared memory and semaphores. For more - discussion see . You may be able + discussion see . You might be able to postpone reconfiguring your kernel by decreasing to reduce the shared memory consumption of PostgreSQL, and/or by reducing @@ -636,18 +636,18 @@ PostgreSQL documentation $ ps -ef | grep postgres depending on your system. If you are certain that no conflicting - server is running, you may remove the lock file mentioned in the + server is running, you can remove the lock file mentioned in the message and try again. - A failure message indicating inability to bind to a port may + A failure message indicating inability to bind to a port might indicate that that port is already in use by some - non-PostgreSQL process. You may also + non-PostgreSQL process. You might also get this error if you terminate postgres and immediately restart it using the same port; in this case, you must simply wait a few seconds until the operating system closes - the port before trying again. Finally, you may get this error if + the port before trying again. Finally, you might get this error if you specify a port number that your operating system considers to be reserved. For example, many versions of Unix consider port numbers under 1024 to be trusted and only permit @@ -665,7 +665,7 @@ PostgreSQL documentation postgres server. Doing so will prevent postgres from freeing the system resources (e.g., shared memory and semaphores) that it holds before - terminating. This may cause problems for starting a fresh + terminating. This might cause problems for starting a fresh postgres run. -- cgit v1.2.3