Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit67cd018

Browse files
committed
Startup is actually start-up.
1 parent883d1cc commit67cd018

18 files changed

+82
-82
lines changed

‎HISTORY

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -232,8 +232,8 @@ Vacuumdb script now supports --all option (Peter E)
232232
ecpg new portable FETCH syntax
233233
Add ecpg EXEC SQL IFDEF, EXEC SQL IFNDEF, EXEC SQL ELSE, EXEC SQL ELIF
234234
and EXEC SQL ENDIF directives
235-
Add pg_ctl script to control backendstartup (Tatsuo)
236-
Add postmaster.opts.default file to storestartup flags (Tatsuo)
235+
Add pg_ctl script to control backendstart-up (Tatsuo)
236+
Add postmaster.opts.default file to storestart-up flags (Tatsuo)
237237
Allow --with-mb=SQL_ASCII
238238
Increase maximum number of index keys to 16 (Bruce)
239239
Increase maximum number of function arguments to 16 (Bruce)
@@ -764,7 +764,7 @@ Update contrib/pginterface/findoidjoins script(Tom)
764764
Major speedup in vacuum of deleted rows with indexes(Vadim)
765765
Allow non-SQL functions to run different versions based on arguments(Tom)
766766
Add -E option that shows actual queries sent by \dt and friends(Masaaki Sakaida)
767-
Add version number instartup banners for psql(Masaaki Sakaida)
767+
Add version number instart-up banners for psql(Masaaki Sakaida)
768768
New contrib/vacuumlo removes large objects not referenced(Peter)
769769
New initialization for table sizes so non-vacuumed tables perform better(Tom)
770770
Improve error messages when a connection is rejected(Tom)
@@ -1059,7 +1059,7 @@ New SERIAL data type, auto-creates sequence/index(Thomas)
10591059
Enable assert checking without a recompile(Massimo)
10601060
User lock enhancements(Massimo)
10611061
New setval() command to set sequence value(Massimo)
1062-
Auto-remove unix socket file onstartup if no postmaster running(Massimo)
1062+
Auto-remove unix socket file onstart-up if no postmaster running(Massimo)
10631063
Conditional trace package(Massimo)
10641064
New UNLISTEN command(Massimo)
10651065
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)
14191419
Add new psql \da, \dd, \df, \do, \dS, and \dT commands(Bruce)
14201420
Enhance psql \z to show sequences(Bruce)
14211421
Show NOT NULL and DEFAULT in psql \d table(Bruce)
1422-
New psql .psqlrc filestartup(Andrew)
1423-
Modify samplestartup script in contrib/linux to show syslog(Thomas)
1422+
New psql .psqlrc filestart-up(Andrew)
1423+
Modify samplestart-up script in contrib/linux to show syslog(Thomas)
14241424
New types for IP and MAC addresses in contrib/ip_and_mac(TomH)
14251425
Unix system time conversions with date/time types in contrib/unixdate(Thomas)
14261426
Update of contrib stuff(Massimo)
@@ -1618,7 +1618,7 @@ Add routines for text trimming on both ends, substring, and string position(Thom
16181618
Added conversion routines circle(box) and poly(circle)(Thomas)
16191619
Allow internal sorts to be stored in memory rather than in files(Bruce & Vadim)
16201620
Allow functions and operators on internally-identical types to succeed(Bruce)
1621-
Speed up backendstartup after profiling analysis(Bruce)
1621+
Speed up backendstart-up after profiling analysis(Bruce)
16221622
Inline frequently called functions for performance(Bruce)
16231623
Reduce open() calls(Bruce)
16241624
psql: Add PAGER for \h and \?,\C fix

‎doc/src/sgml/datatype.sgml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.34 2000/08/24 23:36:28 tgl Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.35 2000/08/29 20:02:07 momjian Exp $
33
-->
44

55
<chapter id="datatype">
@@ -1219,13 +1219,13 @@ January 8 04:05:06 1999 PST
12191219
<listitem>
12201220
<para>
12211221
The <envar>PGDATESTYLE</envar> environment variable used by the backend directly
1222-
on postmasterstartup.
1222+
on postmasterstart-up.
12231223
</para>
12241224
</listitem>
12251225
<listitem>
12261226
<para>
12271227
The <envar>PGDATESTYLE</envar> environment variable used by the frontend libpq
1228-
on sessionstartup.
1228+
on sessionstart-up.
12291229
</para>
12301230
</listitem>
12311231
<listitem>
@@ -1305,7 +1305,7 @@ January 8 04:05:06 1999 PST
13051305
<listitem>
13061306
<para>
13071307
The TZ environment variable used by the backend directly
1308-
on postmasterstartup as the default time zone.
1308+
on postmasterstart-up as the default time zone.
13091309
</para>
13101310
</listitem>
13111311
<listitem>

‎doc/src/sgml/history.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.8 2000/05/02 20:01:51 thomas Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.9 2000/08/29 20:02:07 momjian Exp $
33
-->
44

55
<sect1>
@@ -246,7 +246,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.8 2000/05/02 20:01:51 thom
246246
<listitem>
247247
<para>
248248
Overall backend code speed has been increased by approximately 20-40%,
249-
and backendstartup time has decreased 80% since v6.0 was released.
249+
and backendstart-up time has decreased 80% since v6.0 was released.
250250
</para>
251251
</listitem>
252252
</itemizedlist>

‎doc/src/sgml/indexcost.sgml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/indexcost.sgml,v 2.3 2000/03/31 17:18:26 tgl Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/indexcost.sgml,v 2.4 2000/08/29 20:02:07 momjian Exp $
33
-->
44

55
<chapter>
@@ -111,7 +111,7 @@ amcostestimate (Query *root,
111111
<term>*indexStartupCost</term>
112112
<listitem>
113113
<para>
114-
Set to cost of indexstartup processing
114+
Set to cost of indexstart-up processing
115115
</para>
116116
</listitem>
117117
</varlistentry>
@@ -160,9 +160,9 @@ amcostestimate (Query *root,
160160
</para>
161161

162162
<para>
163-
The "startup cost" is the part of the total scan cost that must be expended
163+
The "start-up cost" is the part of the total scan cost that must be expended
164164
before we can begin to fetch the first tuple. For most indexes this can
165-
be taken as zero, but an index type with a highstartup cost might want
165+
be taken as zero, but an index type with a highstart-up cost might want
166166
to set it nonzero.
167167
</para>
168168

‎doc/src/sgml/installation.sgml

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.15 2000/08/2904:15:43 momjian Exp $ -->
1+
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.16 2000/08/2920:02:07 momjian Exp $ -->
22

33
<chapter id="installation">
44
<title><![%flattext-install-include[<productname>PostgreSQL</> ]]>Installation Instructions</title>
@@ -165,7 +165,7 @@ su - postgres
165165

166166
<para>
167167
On systems which have <productname>PostgreSQL</> started at boot time, there is
168-
probably astartup file that will accomplish the same thing. For
168+
probably astart-up file that will accomplish the same thing. For
169169
example, on a Redhat Linux system one might find that
170170
<programlisting>
171171
/etc/rc.d/init.d/postgres.init stop
@@ -777,7 +777,7 @@ setenv LD_LIBRARY_PATH /usr/local/pgsql/lib
777777
</programlisting>
778778
Replace <literal>/usr/local/pgsql/lib</> with whatever you set
779779
<option><literal>--libdir</></> to in <xref linkend="configure">.
780-
You should put these commands into a shellstartup file such as
780+
You should put these commands into a shellstart-up file such as
781781
<filename>/etc/profile</> or <filename>~/.bash_profile</>.
782782
</para>
783783

@@ -810,7 +810,7 @@ libpq.so.2.1: cannot open shared object file: No such file or directory
810810
add <filename>/usr/local/pgsql/bin</> (or what you set
811811
<option><literal>--bindir</></> to in <xref linkend="configure">)
812812
into your <envar>PATH</>. To do this, add the following to your
813-
shellstartup file, such as <filename>~/.bash_profile</> (or
813+
shellstart-up file, such as <filename>~/.bash_profile</> (or
814814
<filename>/etc/profile</>, if you want it to affect every user):
815815
<programlisting>
816816
PATH=$PATH:/usr/local/pgsql/bin
@@ -824,7 +824,7 @@ set path = ( /usr/local/pgsql/bin path )
824824
<para>
825825
To enable your system to find the <application>man</>
826826
documentation, you need to add a line like the following to a
827-
shellstartup file:
827+
shellstart-up file:
828828
<programlisting>
829829
MANPATH=$MANPATH:/usr/local/pgsql/man
830830
</programlisting>

‎doc/src/sgml/jdbc.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/jdbc.sgml,v 1.11 2000/08/23 05:59:02 thomas Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/jdbc.sgml,v 1.12 2000/08/29 20:02:07 momjian Exp $
33
-->
44

55
<chapter id="jdbc">
@@ -816,7 +816,7 @@ used. Also, only the function's required are entered into this table,
816816
keeping connection times as fast as possible.
817817

818818
The postgresql.LargeObject class performs a query upon it's
819-
startup, and passes the returned ResultSet to the addFunctions()
819+
start-up, and passes the returned ResultSet to the addFunctions()
820820
method here.
821821

822822
Once this has been done, the LargeObject api refers to the

‎doc/src/sgml/libpq.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.39 2000/08/2904:15:43 momjian Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.40 2000/08/2920:02:07 momjian Exp $
33
-->
44

55
<chapter id="libpq-chapter">
@@ -337,7 +337,7 @@ PostgresPollingStatusType *PQconnectPoll(PQconn *conn)
337337
</listitem>
338338
<listitem>
339339
<para>
340-
CONNECTION_AUTH_OK: Received authentication; waiting for backendstartup.
340+
CONNECTION_AUTH_OK: Received authentication; waiting for backendstart-up.
341341
</para>
342342
</listitem>
343343
<listitem>

‎doc/src/sgml/manage-ag.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/manage-ag.sgml,v 2.9 2000/06/30 16:14:21 petere Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/manage-ag.sgml,v 2.10 2000/08/29 20:02:07 momjian Exp $
33
-->
44

55
<chapter id="managing-databases">
@@ -134,8 +134,8 @@ setenv PGDATA2 /home/postgres/data
134134
in csh or tcsh. You have to make sure that this environment
135135
variable is always defined in the server environment, otherwise
136136
you won't be able to access that database. Therefore you probably
137-
want to set it in some sort of shellstartup file or server
138-
startup script.
137+
want to set it in some sort of shellstart-up file or server
138+
start-up script.
139139
</para>
140140

141141
<para>

‎doc/src/sgml/odbc.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/odbc.sgml,v 1.15 2000/05/02 20:01:52 thomas Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/odbc.sgml,v 1.16 2000/08/29 20:02:07 momjian Exp $
33
-->
44

55
<chapter id="odbc">
@@ -1070,7 +1070,7 @@ can't load library 'libodbc.so'\n", 61) = -1 EIO (I/O error)
10701070

10711071
<para>
10721072
You can add information about your
1073-
database login and password to the standard Applixstartup
1073+
database login and password to the standard Applixstart-up
10741074
macro file. This is an example
10751075
<filename>~/axhome/macros/login.am</filename> file:
10761076

‎doc/src/sgml/plan.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/plan.sgml,v 2.3 2000/03/31 17:45:00 tgl Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/plan.sgml,v 2.4 2000/08/29 20:02:07 momjian Exp $
33
-->
44

55
<chapter>
@@ -40,7 +40,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/Attic/plan.sgml,v 2.3 2000/03/31 17:45:00 t
4040
<itemizedlist>
4141
<listitem>
4242
<para>
43-
Estimatedstartup cost (time expended before output scan can start,
43+
Estimatedstart-up cost (time expended before output scan can start,
4444
eg, time to do the sorting in a SORT node).
4545
</para>
4646
</listitem>
@@ -241,7 +241,7 @@ Hash Join (cost=89.60..574.10 rows=100 width=296)
241241
using ye same olde indexscan, stash them into an in-memory hash table,
242242
and then do a sequential scan of tenk2, probing into the hash table
243243
for possible matches of "t1.unique2 = t2.unique2" at each tenk2 tuple.
244-
The cost to read tenk1 and set up the hash table is entirelystartup
244+
The cost to read tenk1 and set up the hash table is entirelystart-up
245245
cost for the hash join, since we won't get any tuples out until we can
246246
start reading tenk2. The total time estimate for the join also
247247
includes a pretty hefty charge for CPU time to probe the hash table

‎doc/src/sgml/problems.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@
114114
<itemizedlist>
115115
<listitem>
116116
<para>
117-
The exact sequence of steps <emphasis>from programstartup</emphasis>
117+
The exact sequence of steps <emphasis>from programstart-up</emphasis>
118118
necessary to reproduce the problem. This should be self-contained;
119119
it is not enough to send in a bare select statement without the
120120
preceeding create table and insert statements, if the output should
@@ -125,7 +125,7 @@
125125
query-language related problems is a file that can be run through the
126126
<application>psql</application> frontend
127127
that shows the problem. (Be sure to not have anything in your
128-
<filename>~/.psqlrc</filename>startup file.) You are encouraged to
128+
<filename>~/.psqlrc</filename>start-up file.) You are encouraged to
129129
minimize the size of your example, but this is not absolutely necessary.
130130
If the bug is reproduceable, we'll find it either way.
131131
</para>
@@ -176,7 +176,7 @@
176176

177177
<listitem>
178178
<para>
179-
Any command line options and otherstartup options, including concerned
179+
Any command line options and otherstart-up options, including concerned
180180
environment variables or configuration files that you changed from the
181181
default. Again, be exact. If you are using a pre-packaged
182182
distribution that starts the database server at boot time, you should try

‎doc/src/sgml/protocol.sgml

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ have different roles but may be implemented by the same executable.
4747
</para>
4848

4949
<Para>
50-
A frontend sends astartup packet to the postmaster. This includes the names
50+
A frontend sends astart-up packet to the postmaster. This includes the names
5151
of the user and the database the user wants to connect to. The postmaster then
5252
uses this, and the information in the <filename>pg_hba.conf</filename>
5353
file
@@ -60,7 +60,7 @@ and responds to the frontend accordingly.
6060
The frontend then sends any required authentication information. Once the
6161
postmaster validates this it responds to the frontend that it is authenticated
6262
and hands over the connection to a backend. The backend then sends a message
63-
indicating successfulstartup (normal case) or failure (for example, an
63+
indicating successfulstart-up (normal case) or failure (for example, an
6464
invalid database name).
6565
</para>
6666

@@ -91,17 +91,17 @@ itself. The difference is historical.
9191
<Para>
9292
This section describes the message flow. There are four different types of
9393
flows depending on the state of the connection:
94-
startup, query, function call, and termination.
94+
start-up, query, function call, and termination.
9595
There are also special provisions for notification responses and command
96-
cancellation, which can occur at any time after thestartup phase.
96+
cancellation, which can occur at any time after thestart-up phase.
9797
</para>
9898

9999

100100
<Sect2>
101-
<Title>Startup</Title>
101+
<Title>Start-up</Title>
102102

103103
<Para>
104-
Startup is divided into an authentication phase and a backendstartup phase.
104+
Start-up is divided into an authentication phase and a backendstart-up phase.
105105
</para>
106106

107107
<Para>
@@ -197,8 +197,8 @@ postmaster, then it should immediately close the connection.
197197
<Para>
198198
After sending AuthenticationOk, the postmaster attempts to launch a backend
199199
process. Since this might fail, or the backend might encounter a failure
200-
duringstartup, the frontend must wait for the backend to acknowledge
201-
successfulstartup. The frontend should send no messages at this point.
200+
duringstart-up, the frontend must wait for the backend to acknowledge
201+
successfulstart-up. The frontend should send no messages at this point.
202202
The possible messages from the backend during this phase are:
203203

204204
<VariableList>
@@ -208,7 +208,7 @@ The possible messages from the backend during this phase are:
208208
</Term>
209209
<ListItem>
210210
<Para>
211-
This message is issued after successful backendstartup.
211+
This message is issued after successful backendstart-up.
212212
It provides secret-key data that the frontend must save
213213
if it wants to be able to issue cancel requests later.
214214
The frontend should not respond to this message, but should
@@ -222,7 +222,7 @@ The possible messages from the backend during this phase are:
222222
</Term>
223223
<ListItem>
224224
<Para>
225-
Backendstartup is successful. The frontend may now issue
225+
Backendstart-up is successful. The frontend may now issue
226226
query or function call messages.
227227
</Para>
228228
</ListItem>
@@ -233,7 +233,7 @@ The possible messages from the backend during this phase are:
233233
</Term>
234234
<ListItem>
235235
<Para>
236-
Backendstartup failed. The connection is closed after
236+
Backendstart-up failed. The connection is closed after
237237
sending this message.
238238
</Para>
239239
</ListItem>
@@ -257,8 +257,8 @@ The possible messages from the backend during this phase are:
257257
The ReadyForQuery message is the same one that the backend will issue after
258258
each query cycle. Depending on the coding needs of the frontend, it is
259259
reasonable to consider ReadyForQuery as starting a query cycle (and then
260-
BackendKeyData indicates successful conclusion of thestartup phase),
261-
or to consider ReadyForQuery as ending thestartup phase and each subsequent
260+
BackendKeyData indicates successful conclusion of thestart-up phase),
261+
or to consider ReadyForQuery as ending thestart-up phase and each subsequent
262262
query cycle.
263263
</para>
264264
</sect2>
@@ -516,7 +516,7 @@ whenever a notify(l) command is executed for the same notification name.
516516

517517
<Para>
518518
Notification responses are permitted at any point in the protocol (after
519-
startup), except within another backend message. Thus, the frontend
519+
start-up), except within another backend message. Thus, the frontend
520520
must be prepared to recognize a NotificationResponse message whenever it is
521521
expecting any message. Indeed, it should be able to handle
522522
NotificationResponse messages even when it is not engaged in a query.
@@ -568,7 +568,7 @@ reasons, no direct reply is made to the cancel request message.
568568

569569
<Para>
570570
A CancelRequest message will be ignored unless it contains the same key data
571-
(PID and secret key) passed to the frontend during connectionstartup. If the
571+
(PID and secret key) passed to the frontend during connectionstart-up. If the
572572
request matches the PID and secret key for a currently executing backend, the
573573
postmaster signals the backend to abort processing of the current query.
574574
</para>

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp