mirror of
https://github.com/postgres/postgres.git
synced 2025-12-21 05:21:08 +03:00
Startup is actually start-up.
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/explain.sgml,v 1.9 2000/02/15 23:37:49 tgl Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/explain.sgml,v 1.10 2000/08/29 20:02:09 momjian Exp $
|
||||
Postgres documentation
|
||||
-->
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgctl-ref.sgml,v 1.6 2000/07/22 04:30:27 momjian Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgctl-ref.sgml,v 1.7 2000/08/29 20:02:09 momjian Exp $
|
||||
Postgres documentation
|
||||
-->
|
||||
|
||||
@@ -119,7 +119,7 @@ pg_ctl [-D <replaceable class="parameter">datadir</replaceable>] status
|
||||
<para>
|
||||
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.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.35 2000/07/22 04:45:09 momjian Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.36 2000/08/29 20:02:09 momjian Exp $
|
||||
Postgres documentation
|
||||
-->
|
||||
|
||||
@@ -1296,7 +1296,7 @@ Access permissions for database "test"
|
||||
In general, both will do what you expect, but using <literal>-f</literal>
|
||||
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.
|
||||
</para>
|
||||
@@ -1503,7 +1503,7 @@ Access permissions for database "test"
|
||||
Performs a variable assignment, like the <command>\set</command> 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.
|
||||
</para>
|
||||
</listitem>
|
||||
@@ -1557,7 +1557,7 @@ Access permissions for database "test"
|
||||
<term>-X, --no-psqlrc</term>
|
||||
<listitem>
|
||||
<para>
|
||||
Do not read the startup file <filename>~/.psqlrc</filename>.
|
||||
Do not read the start-up file <filename>~/.psqlrc</filename>.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
@@ -1646,7 +1646,7 @@ bar
|
||||
<listitem>
|
||||
<para>
|
||||
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.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
@@ -1657,7 +1657,7 @@ bar
|
||||
<para>
|
||||
If set to <quote><literal>all</literal></quote>, 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
|
||||
<option>-a</option>. If set to <quote><literal>queries</literal></quote>,
|
||||
<application>psql</application> merely prints all queries as they are sent to the
|
||||
backend. The option for this is <option>-e</option>.
|
||||
@@ -1728,7 +1728,7 @@ bar
|
||||
<listitem>
|
||||
<para>
|
||||
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.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
@@ -1816,7 +1816,7 @@ bar
|
||||
<listitem>
|
||||
<para>
|
||||
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.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
@@ -1867,7 +1867,7 @@ bar
|
||||
<listitem>
|
||||
<para>
|
||||
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.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/set.sgml,v 1.47 2000/08/07 00:51:18 tgl Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/set.sgml,v 1.48 2000/08/29 20:02:09 momjian Exp $
|
||||
Postgres documentation
|
||||
-->
|
||||
|
||||
@@ -165,7 +165,7 @@ SET TIME ZONE { '<replaceable class="PARAMETER">timezone</replaceable>' | LOCAL
|
||||
Setting the <envar>PGDATESTYLE</envar> 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.
|
||||
</member>
|
||||
<member>
|
||||
Running postmaster using the option <option>-o -e</option> to
|
||||
@@ -288,7 +288,7 @@ SELECT setseed(<replaceable>value</replaceable>);
|
||||
<para>
|
||||
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.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
@@ -341,7 +341,7 @@ SELECT setseed(<replaceable>value</replaceable>);
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><computeroutput>ERROR: <replaceable>name</replaceable> can only be set at startup</computeroutput></term>
|
||||
<term><computeroutput>ERROR: <replaceable>name</replaceable> can only be set at start-up</computeroutput></term>
|
||||
<listitem>
|
||||
<para>
|
||||
Some parameters are fixed once the server is started.
|
||||
|
||||
Reference in New Issue
Block a user