Startup is actually start-up.

Author: bmomjian

HISTORY

@@ -232,8 +232,8 @@ Vacuumdb script now supports --all option (Peter E)
 ecpg new portable FETCH syntax
 Add ecpg EXEC SQL IFDEF, EXEC SQL IFNDEF, EXEC SQL ELSE, EXEC SQL ELIF 
 	and EXEC SQL ENDIF directives
-Add pg_ctl script to control backend startup (Tatsuo)
-Add postmaster.opts.default file to store startup flags (Tatsuo)
+Add pg_ctl script to control backend start-up (Tatsuo)
+Add postmaster.opts.default file to store start-up flags (Tatsuo)
 Allow --with-mb=SQL_ASCII
 Increase maximum number of index keys to 16 (Bruce)
 Increase maximum number of function arguments to 16 (Bruce)
@@ -764,7 +764,7 @@ Update contrib/pginterface/findoidjoins script(Tom)
 Major speedup in vacuum of deleted rows with indexes(Vadim)
 Allow non-SQL functions to run different versions based on arguments(Tom)
 Add -E option that shows actual queries sent by \dt and friends(Masaaki Sakaida)
-Add version number in startup banners for psql(Masaaki Sakaida)
+Add version number in start-up banners for psql(Masaaki Sakaida)
 New contrib/vacuumlo removes large objects not referenced(Peter)
 New initialization for table sizes so non-vacuumed tables perform better(Tom)
 Improve error messages when a connection is rejected(Tom)
@@ -1059,7 +1059,7 @@ New SERIAL data type, auto-creates sequence/index(Thomas)
 Enable assert checking without a recompile(Massimo)
 User lock enhancements(Massimo)
 New setval() command to set sequence value(Massimo)
-Auto-remove unix socket file on startup if no postmaster running(Massimo)
+Auto-remove unix socket file on start-up if no postmaster running(Massimo)
 Conditional trace package(Massimo)
 New UNLISTEN command(Massimo)
 Psql and libpq now compile under win32 using win32.mak(Magnus)
@@ -1419,8 +1419,8 @@ New LOCK command and lock manual page describing deadlocks(Bruce)
 Add new psql \da, \dd, \df, \do, \dS, and \dT commands(Bruce)
 Enhance psql \z to show sequences(Bruce)
 Show NOT NULL and DEFAULT in psql \d table(Bruce)
-New psql .psqlrc file startup(Andrew)
-Modify sample startup script in contrib/linux to show syslog(Thomas)
+New psql .psqlrc file start-up(Andrew)
+Modify sample start-up script in contrib/linux to show syslog(Thomas)
 New types for IP and MAC addresses in contrib/ip_and_mac(TomH)
 Unix system time conversions with date/time types in contrib/unixdate(Thomas)
 Update of contrib stuff(Massimo)
@@ -1618,7 +1618,7 @@ Add routines for text trimming on both ends, substring, and string position(Thom
 Added conversion routines circle(box) and poly(circle)(Thomas)
 Allow internal sorts to be stored in memory rather than in files(Bruce & Vadim)
 Allow functions and operators on internally-identical types to succeed(Bruce)
-Speed up backend startup after profiling analysis(Bruce)
+Speed up backend start-up after profiling analysis(Bruce)
 Inline frequently called functions for performance(Bruce)
 Reduce open() calls(Bruce)
 psql:  Add PAGER for \h and \?,\C fix

doc/src/sgml/datatype.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.34 2000/08/24 23:36:28 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.35 2000/08/29 20:02:07 momjian Exp $
 -->
 
  <chapter id="datatype">
@@ -1219,13 +1219,13 @@ January 8 04:05:06 1999 PST
       <listitem>
        <para>
 	The <envar>PGDATESTYLE</envar> environment variable used by the backend directly 
-	on postmaster startup.
+	on postmaster start-up.
        </para>
       </listitem>
       <listitem>
        <para>
 	The <envar>PGDATESTYLE</envar> environment variable used by the frontend libpq 
-	on session startup.
+	on session start-up.
        </para>
       </listitem>
       <listitem>
@@ -1305,7 +1305,7 @@ January 8 04:05:06 1999 PST
       <listitem>
        <para>
 	The TZ environment variable used by the backend directly
-	on postmaster startup as the default time zone.
+	on postmaster start-up as the default time zone.
        </para>
       </listitem>
       <listitem>

doc/src/sgml/history.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.8 2000/05/02 20:01:51 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.9 2000/08/29 20:02:07 momjian Exp $
 -->
 
 <sect1>
@@ -246,7 +246,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.8 2000/05/02 20:01:51 thom
    <listitem>
     <para>
      Overall backend code speed has been increased by approximately 20-40%, 
-     and backend startup time has decreased 80% since v6.0 was released.
+     and backend start-up time has decreased 80% since v6.0 was released.
     </para>
    </listitem>
   </itemizedlist>

doc/src/sgml/indexcost.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/indexcost.sgml,v 2.3 2000/03/31 17:18:26 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/Attic/indexcost.sgml,v 2.4 2000/08/29 20:02:07 momjian Exp $
 -->
 
  <chapter>
@@ -111,7 +111,7 @@ amcostestimate (Query *root,
      <term>*indexStartupCost</term>
      <listitem>
       <para>
-       Set to cost of index startup processing
+       Set to cost of index start-up processing
       </para>
      </listitem>
     </varlistentry>
@@ -160,9 +160,9 @@ amcostestimate (Query *root,
   </para>
 
   <para>
-   The "startup cost" is the part of the total scan cost that must be expended
+   The "start-up cost" is the part of the total scan cost that must be expended
    before we can begin to fetch the first tuple.  For most indexes this can
-   be taken as zero, but an index type with a high startup cost might want
+   be taken as zero, but an index type with a high start-up cost might want
    to set it nonzero.
   </para>
 

doc/src/sgml/installation.sgml

@@ -1,4 +1,4 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.15 2000/08/29 04:15:43 momjian Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.16 2000/08/29 20:02:07 momjian Exp $ -->
 
 <chapter id="installation">
  <title><![%flattext-install-include[<productname>PostgreSQL</> ]]>Installation Instructions</title>
@@ -165,7 +165,7 @@ su - postgres
 
     <para>
      On systems which have <productname>PostgreSQL</> started at boot time, there is
-     probably a startup file that will accomplish the same thing. For
+     probably a start-up file that will accomplish the same thing. For
      example, on a Redhat Linux system one might find that
 <programlisting>
 /etc/rc.d/init.d/postgres.init stop
@@ -777,7 +777,7 @@ setenv LD_LIBRARY_PATH /usr/local/pgsql/lib
 </programlisting>
     Replace <literal>/usr/local/pgsql/lib</> with whatever you set
     <option><literal>--libdir</></> to in <xref linkend="configure">.
-    You should put these commands into a shell startup file such as
+    You should put these commands into a shell start-up file such as
     <filename>/etc/profile</> or <filename>~/.bash_profile</>.
    </para>
 
@@ -810,7 +810,7 @@ libpq.so.2.1: cannot open shared object file: No such file or directory
     add <filename>/usr/local/pgsql/bin</> (or what you set
     <option><literal>--bindir</></> to in <xref linkend="configure">)
     into your <envar>PATH</>. To do this, add the following to your
-    shell startup file, such as <filename>~/.bash_profile</> (or
+    shell start-up file, such as <filename>~/.bash_profile</> (or
     <filename>/etc/profile</>, if you want it to affect every user):
 <programlisting>
 PATH=$PATH:/usr/local/pgsql/bin
@@ -824,7 +824,7 @@ set path = ( /usr/local/pgsql/bin path )
    <para>
     To enable your system to find the <application>man</>
     documentation, you need to add a line like the following to a
-    shell startup file:
+    shell start-up file:
 <programlisting>
 MANPATH=$MANPATH:/usr/local/pgsql/man
 </programlisting>

doc/src/sgml/jdbc.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/jdbc.sgml,v 1.11 2000/08/23 05:59:02 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/Attic/jdbc.sgml,v 1.12 2000/08/29 20:02:07 momjian Exp $
 -->
 
  <chapter id="jdbc">
@@ -816,7 +816,7 @@ used. Also, only the function's required are entered into this table,
 keeping connection times as fast as possible.
 
           The postgresql.LargeObject class performs a query upon it's 
-startup, and passes the returned ResultSet to the addFunctions() 
+start-up, and passes the returned ResultSet to the addFunctions() 
 method here.
 
           Once this has been done, the LargeObject api refers to the 

doc/src/sgml/libpq.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.39 2000/08/29 04:15:43 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.40 2000/08/29 20:02:07 momjian Exp $
 -->
 
  <chapter id="libpq-chapter">
@@ -337,7 +337,7 @@ PostgresPollingStatusType *PQconnectPoll(PQconn *conn)
      </listitem>
      <listitem>
       <para>
-      CONNECTION_AUTH_OK: Received authentication; waiting for backend startup.
+      CONNECTION_AUTH_OK: Received authentication; waiting for backend start-up.
       </para>
      </listitem>
      <listitem>

doc/src/sgml/manage-ag.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/manage-ag.sgml,v 2.9 2000/06/30 16:14:21 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/manage-ag.sgml,v 2.10 2000/08/29 20:02:07 momjian Exp $
 -->
 
 <chapter id="managing-databases">
@@ -134,8 +134,8 @@ setenv PGDATA2 /home/postgres/data
     in csh or tcsh. You have to make sure that this environment
     variable is always defined in the server environment, otherwise
     you won't be able to access that database. Therefore you probably
-    want to set it in some sort of shell startup file or server
-    startup script.
+    want to set it in some sort of shell start-up file or server
+    start-up script.
    </para>
 
    <para>

doc/src/sgml/odbc.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/odbc.sgml,v 1.15 2000/05/02 20:01:52 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/Attic/odbc.sgml,v 1.16 2000/08/29 20:02:07 momjian Exp $
 -->
 
  <chapter id="odbc">
@@ -1070,7 +1070,7 @@ can't load library 'libodbc.so'\n", 61) = -1 EIO (I/O error)
 
     <para>
      You can add information about your
-     database login and password to the standard Applix startup
+     database login and password to the standard Applix start-up
      macro file. This is an example 
      <filename>~/axhome/macros/login.am</filename> file:
 

doc/src/sgml/plan.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/plan.sgml,v 2.3 2000/03/31 17:45:00 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/Attic/plan.sgml,v 2.4 2000/08/29 20:02:07 momjian Exp $
 -->
 
  <chapter>
@@ -40,7 +40,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/Attic/plan.sgml,v 2.3 2000/03/31 17:45:00 t
     <itemizedlist>
      <listitem>
       <para>
-       Estimated startup cost (time expended before output scan can start,
+       Estimated start-up cost (time expended before output scan can start,
        eg, time to do the sorting in a SORT node).
       </para>
      </listitem>
@@ -241,7 +241,7 @@ Hash Join  (cost=89.60..574.10 rows=100 width=296)
     using ye same olde indexscan, stash them into an in-memory hash table,
     and then do a sequential scan of tenk2, probing into the hash table
     for possible matches of "t1.unique2 = t2.unique2" at each tenk2 tuple.
-    The cost to read tenk1 and set up the hash table is entirely startup
+    The cost to read tenk1 and set up the hash table is entirely start-up
     cost for the hash join, since we won't get any tuples out until we can
     start reading tenk2.  The total time estimate for the join also
     includes a pretty hefty charge for CPU time to probe the hash table