From d258ba01ec601f655137468bd484153eb369e92d Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Mon, 24 Mar 2003 14:32:51 +0000 Subject: Another big editing pass for consistent content and presentation. --- doc/src/sgml/ref/postgres-ref.sgml | 77 +++++++++++++++++++------------------- 1 file changed, 38 insertions(+), 39 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 7b282eb295a..8d1bc512ebf 100644 --- a/doc/src/sgml/ref/postgres-ref.sgml +++ b/doc/src/sgml/ref/postgres-ref.sgml @@ -1,5 +1,5 @@ @@ -62,7 +62,7 @@ PostgreSQL documentation -tpaplex -S sort-mem - -v protocol-version + -v protocol -W seconds --name=value @@ -72,7 +72,7 @@ PostgreSQL documentation Description - The postgres executable is the actual + The postgres executable is the actual PostgreSQL server process that processes queries. It is normally not called directly; instead a multiuser server is started. @@ -80,7 +80,7 @@ PostgreSQL documentation The second form above is how - postgres is invoked by the postgres is invoked by the (only conceptually, since both postmaster and postgres are in fact the same program); it @@ -94,15 +94,15 @@ PostgreSQL documentation When invoked in interactive mode from the shell, the user can enter queries and the results will be printed to the screen, but in a form that is more useful for developers than end users. But note - that running a single-user backend is not truly suitable for + that running a single-user server is not truly suitable for debugging the server since no realistic interprocess communication and locking will happen. - When running a stand-alone backend, the session user will be set to + When running a stand-alone server, the session user will be set to the user with ID 1. This user does not actually have to exist, so - a stand-alone backend can be used to manually recover from certain + a stand-alone server can be used to manually recover from certain kinds of accidental damage to the system catalogs. Implicit superuser powers are granted to the user with ID 1 in stand-alone mode. @@ -113,11 +113,11 @@ PostgreSQL documentation Options - When postgres is started by a postgres is started by a then it inherits all options set by the latter. Additionally, - postgres-specific options can be passed - from the postmaster with the + postgres-specific options can be passed + from the postmaster with the switch. @@ -129,7 +129,7 @@ PostgreSQL documentation variable PGOPTIONS is set, then libpq-based clients will pass that string to the server, which will interpret it as - postgres command-line options. + postgres command-line options. @@ -138,10 +138,10 @@ PostgreSQL documentation The options , , , , , - , and , and have the same meanings as the except that - 0 prevents the debugging level of - the postmaster from being propagated to the backend. + -d 0 prevents the server log level of + the postmaster from being propagated to postgres. @@ -162,12 +162,12 @@ PostgreSQL documentation filename - Sends all debugging and error output to + Send all server log output to filename. - If the backend is running under the - postmaster, this option is ignored, + If postgres is running under the + postmaster, this option is ignored, and the stderr inherited from the - postmaster is used. + postmaster is used. @@ -176,7 +176,7 @@ PostgreSQL documentation - Ignore system indexes while scanning/updating system tuples. The + Ignore system indexes while scanning/updating system tables. The REINDEX command for system tables/indexes requires this option to be used. @@ -187,7 +187,7 @@ PostgreSQL documentation - Print time information and other statistics at the end of each query. + Print time information and other statistics at the end of each command. This is useful for benchmarking or for use in tuning the number of buffers. @@ -200,7 +200,7 @@ PostgreSQL documentation Specifies the amount of memory to be used by internal sorts and hashes before resorting to temporary disk files. The value is specified in - kilobytes, and defaults to 512 kilobytes. Note that for a complex query, + kilobytes, and defaults to 1024. Note that for a complex query, several sorts and/or hashes might be running in parallel, and each one will be allowed to use as much as sort-mem kilobytes @@ -230,7 +230,7 @@ PostgreSQL documentation - Echo all queries. + Echo all commands. @@ -239,7 +239,7 @@ PostgreSQL documentation - Disables use of newline as a query delimiter. + Disables use of newline as a statement delimiter. @@ -268,6 +268,7 @@ PostgreSQL documentation disable sequential and index scans respectively, while n, m, and h disable nested-loop, merge and hash joins respectively. + @@ -277,7 +278,6 @@ PostgreSQL documentation plan types if it has any other alternative. - @@ -295,7 +295,7 @@ PostgreSQL documentation Allows the structure of system tables to be modified. This is - used by initdb. + used by initdb. @@ -304,9 +304,8 @@ PostgreSQL documentation database - Indicates that this server has been started by a - postmaster and makes different - assumptions about buffer pool management, file descriptors, + Indicates that this process has been started by a + postmaster and specifies the database to use. etc. @@ -339,7 +338,7 @@ PostgreSQL documentation As soon as this option is encountered, the process sleeps for the specified amount of seconds. This gives developers time - to attach a debugger to the backend process. + to attach a debugger to the server process. @@ -375,10 +374,10 @@ PostgreSQL documentation To stop a running query use the SIGINT signal. To - tell postgres to reread the config file, + tell postgres to reread the configuration file, use a SIGHUP signal. The - postmaster uses SIGTERM - to tell a postgres process to quit normally and + postmaster uses SIGTERM + to tell a postgres process to quit normally and SIGQUIT to terminate without the normal cleanup. These should not be used by users. @@ -389,17 +388,17 @@ PostgreSQL documentation Usage - Start a stand-alone backend with a command like + Start a stand-alone server with a command like -postgres -D $PGDATA other-options my_database +postgres -D /usr/local/pgsql/data other-options my_database - Provide the correct path to the database area with - Normally, the stand-alone backend treats newline as the command + Normally, the stand-alone server treats newline as the command entry terminator; there is no intelligence about semicolons, as there is in psql. To continue a command across multiple lines, you must type backslash just before each @@ -408,9 +407,9 @@ PostgreSQL documentation But if you use the @@ -422,7 +421,7 @@ PostgreSQL documentation - Note that the stand-alone backend does not provide sophisticated + Note that the stand-alone server does not provide sophisticated line-editing features (no command history, for example). -- cgit v1.2.3