From 67cd018e772e31157030dcfbb9f6c01d9c308658 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 29 Aug 2000 20:02:09 +0000 Subject: Startup is actually start-up. --- doc/src/sgml/ref/explain.sgml | 6 +++--- doc/src/sgml/ref/pgctl-ref.sgml | 4 ++-- doc/src/sgml/ref/psql-ref.sgml | 18 +++++++++--------- doc/src/sgml/ref/set.sgml | 8 ++++---- 4 files changed, 18 insertions(+), 18 deletions(-) (limited to 'doc/src/sgml/ref') diff --git a/doc/src/sgml/ref/explain.sgml b/doc/src/sgml/ref/explain.sgml index e7622fb026..c31935b323 100644 --- a/doc/src/sgml/ref/explain.sgml +++ b/doc/src/sgml/ref/explain.sgml @@ -1,5 +1,5 @@ @@ -114,10 +114,10 @@ EXPLAIN The most critical part of the display is the estimated query execution cost, which is the planner's guess at how long it will take to run the query (measured in units of disk page fetches). Actually two numbers - are shown: the startup time before the first tuple can be returned, and + are shown: the start-up time before the first tuple can be returned, and the total time to return all the tuples. For most queries the total time is what matters, but in contexts such as an EXISTS sub-query the planner - will choose the smallest startup time instead of the smallest total time + will choose the smallest start-up time instead of the smallest total time (since the executor will stop after getting one tuple, anyway). Also, if you limit the number of tuples to return with a LIMIT clause, the planner makes an appropriate interpolation between the endpoint diff --git a/doc/src/sgml/ref/pgctl-ref.sgml b/doc/src/sgml/ref/pgctl-ref.sgml index c85b5e31e1..4b0e81b448 100644 --- a/doc/src/sgml/ref/pgctl-ref.sgml +++ b/doc/src/sgml/ref/pgctl-ref.sgml @@ -1,5 +1,5 @@ @@ -119,7 +119,7 @@ pg_ctl [-D datadir] status Immediate mode sends SIGUSR1 to the backends and lets them abort. In this case, database recovery - will be necessary on the next startup. + will be necessary on the next start-up. diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml index fccc7ef5c6..60a5e95f40 100644 --- a/doc/src/sgml/ref/psql-ref.sgml +++ b/doc/src/sgml/ref/psql-ref.sgml @@ -1,5 +1,5 @@ @@ -1296,7 +1296,7 @@ Access permissions for database "test" In general, both will do what you expect, but using -f enables some nice features such as error messages with line numbers. There is also a slight chance that using this option will reduce - the startup overhead. On the other hand, the variant using the shell's + the start-up overhead. On the other hand, the variant using the shell's input redirection is (in theory) guaranteed to yield exactly the same output that you would have gotten had you entered everything by hand. @@ -1503,7 +1503,7 @@ Access permissions for database "test" Performs a variable assignment, like the \set internal command. Note that you must separate name and value, if any, by an equal sign on the command line. To unset a variable, leave off the equal sign. These assignments are done - during a very early state of startup, so variables reserved for internal purposes + during a very early state of start-up, so variables reserved for internal purposes might get overwritten later. @@ -1557,7 +1557,7 @@ Access permissions for database "test" -X, --no-psqlrc - Do not read the startup file ~/.psqlrc. + Do not read the start-up file ~/.psqlrc. @@ -1646,7 +1646,7 @@ bar The name of the database you are currently connected to. This is set every time - you connect to a database (including program startup), but can be unset. + you connect to a database (including program start-up), but can be unset. @@ -1657,7 +1657,7 @@ bar If set to all, all lines entered or from a script are written to the standard output before they - are parsed or executed. To specify this on program startup, use the switch + are parsed or executed. To specify this on program start-up, use the switch . If set to queries, psql merely prints all queries as they are sent to the backend. The option for this is . @@ -1728,7 +1728,7 @@ bar The database server host you are currently connected to. This is set every time - you connect to a database (including program startup), but can be unset. + you connect to a database (including program start-up), but can be unset. @@ -1816,7 +1816,7 @@ bar The database server port to which you are currently connected. This is set every time - you connect to a database (including program startup), but can be unset. + you connect to a database (including program start-up), but can be unset. @@ -1867,7 +1867,7 @@ bar The database user you are currently connected as. This is set every time - you connect to a database (including program startup), but can be unset. + you connect to a database (including program start-up), but can be unset. diff --git a/doc/src/sgml/ref/set.sgml b/doc/src/sgml/ref/set.sgml index b76570d5de..b183db7fef 100644 --- a/doc/src/sgml/ref/set.sgml +++ b/doc/src/sgml/ref/set.sgml @@ -1,5 +1,5 @@ @@ -165,7 +165,7 @@ SET TIME ZONE { 'timezone' | LOCAL Setting the PGDATESTYLE environment variable. If PGDATESTYLE is set in the frontend environment of a client based on libpq, libpq will automatically set DATESTYLE to the - value of PGDATESTYLE during connection startup. + value of PGDATESTYLE during connection start-up. Running postmaster using the option to @@ -288,7 +288,7 @@ SELECT setseed(value); If the PGTZ environment variable is set in the frontend environment of a client based on libpq, libpq will automatically - set TIMEZONE to the value of PGTZ during connection startup. + set TIMEZONE to the value of PGTZ during connection start-up. @@ -341,7 +341,7 @@ SELECT setseed(value); - ERROR: name can only be set at startup + ERROR: name can only be set at start-up Some parameters are fixed once the server is started. -- cgit v1.2.1