pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feed"Backend server" term usage
5+ messages / 3 participants
[nested] [flat]
* "Backend server" term usage
@ 2011-03-11 14:42 Bruce Momjian <bruce@momjian.us>
0 siblings, 2 replies; 5+ messages in thread
From: Bruce Momjian @ 2011-03-11 14:42 UTC (permalink / raw)
To: Alvaro Herrera <alvherre@commandprompt.com>; +Cc: Dmitriy Igrishin <dmitigr@gmail.com>; Robert Haas <robertmhaas@gmail.com>; pgsql-docs
Alvaro Herrera wrote:
> Excerpts from Dmitriy Igrishin's message of dom feb 20 06:19:19 -0300 2011:
>
> > Better, undoubtedly.
> > Another alternative is just "server". Why? Well, for consistency, e.g. with
> > http://www.postgresql.org/docs/9.0/static/errcodes-appendix.html
> > Here you may see phrase "All messages emitted by the PostgreSQL server ..."
> > and furthermore, there are some SQL standard's "SQLSTATE" code
> > which name includes "server" rather than "backend":
> > SQLSERVER REJECTED ESTABLISHMENT OF SQLCONNECTION
> > But anyway, phrase "backend server" is incorrect.
>
> Maybe some cleanup would be good, but in that case please provide a
> specific patch. The replacement suggested in the email that started
> this thread seems OK, but wholesale replacement of the phrase "backend
> server" with something else is likely to introduce as many mistakes as
> it would fix. For example, the description of postgres' -T switch would
> then be wrong.
>
> I think using the protocol chapter as reference for terms to use is a
> bad idea -- it's one of the most obscure chapters in the documentation.
OK, attached is my proposed patch; it mostly changes "backend server"
to "backend process".
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
Attachments:
/rtmp/backend.diff (text/x-diff, 5.2K) download
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 59b4011..1c223cb 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -1612,7 +1612,7 @@ int PQsocket(const PGconn *conn);
<para>
Returns the process <acronym>ID</acronym>
(PID)<indexterm><primary>PID</><secondary>determining PID of
- server process</><tertiary>in libpq</></> of the backend server
+ server process</><tertiary>in libpq</></> of the backend
process handling this connection.
<synopsis>
diff --git a/doc/src/sgml/problems.sgml b/doc/src/sgml/problems.sgml
index a65baa3..3f79c6e 100644
--- a/doc/src/sgml/problems.sgml
+++ b/doc/src/sgml/problems.sgml
@@ -78,7 +78,7 @@
</listitem>
</itemizedlist>
- Here <quote>program</quote> refers to any executable, not only the backend server.
+ Here <quote>program</quote> refers to any executable, not only the backend process.
</para>
<para>
@@ -280,9 +280,9 @@
When writing a bug report, please avoid confusing terminology.
The software package in total is called <quote>PostgreSQL</quote>,
sometimes <quote>Postgres</quote> for short. If you
- are specifically talking about the backend server, mention that, do not
+ are specifically talking about the backend process, mention that, do not
just say <quote>PostgreSQL crashes</quote>. A crash of a single
- backend server process is quite different from crash of the parent
+ backend process is quite different from crash of the parent
<quote>postgres</> process; please don't say <quote>the server
crashed</> when you mean a single backend process went down, nor vice versa.
Also, client programs such as the interactive frontend <quote><application>psql</application></quote>
diff --git a/doc/src/sgml/query.sgml b/doc/src/sgml/query.sgml
index 681d08a..f4fbf11 100644
--- a/doc/src/sgml/query.sgml
+++ b/doc/src/sgml/query.sgml
@@ -264,8 +264,8 @@ INSERT INTO weather (date, city, temp_hi, temp_lo)
COPY weather FROM '/home/user/weather.txt';
</programlisting>
- where the file name for the source file must be available to the
- backend server machine, not the client, since the backend server
+ where the file name for the source file must be available on the
+ machine running the backend process, not the client, since the backend process
reads the file directly. You can read more about the
<command>COPY</command> command in <xref linkend="sql-copy">.
</para>
diff --git a/doc/src/sgml/ref/pg_ctl-ref.sgml b/doc/src/sgml/ref/pg_ctl-ref.sgml
index 608749f..626ed1f 100644
--- a/doc/src/sgml/ref/pg_ctl-ref.sgml
+++ b/doc/src/sgml/ref/pg_ctl-ref.sgml
@@ -134,7 +134,7 @@ PostgreSQL documentation
<application>pg_ctl</application> is a utility for initializing a
<productname>PostgreSQL</productname> database cluster, starting,
stopping, or restarting the <productname>PostgreSQL</productname>
- backend server (<xref linkend="app-postgres">), or displaying the
+ database server (<xref linkend="app-postgres">), or displaying the
status of a running server. Although the server can be started
manually, <application>pg_ctl</application> encapsulates tasks such
as redirecting log output and properly detaching from the terminal
diff --git a/src/backend/libpq/pqsignal.c b/src/backend/libpq/pqsignal.c
index 31e37e9..0fee280 100644
--- a/src/backend/libpq/pqsignal.c
+++ b/src/backend/libpq/pqsignal.c
@@ -22,7 +22,7 @@
* how to handle signalling.
*
* signal(2) handling - this is here because it affects some of
- * the frontend commands as well as the backend server.
+ * the frontend commands as well as the backend processes.
*
* Ultrix and SunOS provide BSD signal(2) semantics by default.
*
diff --git a/src/backend/main/main.c b/src/backend/main/main.c
index 5d07788..43d182b 100644
--- a/src/backend/main/main.c
+++ b/src/backend/main/main.c
@@ -310,7 +310,7 @@ help(const char *progname)
printf(_(" -O allow system table structure changes\n"));
printf(_(" -P disable system indexes\n"));
printf(_(" -t pa|pl|ex show timings after each query\n"));
- printf(_(" -T send SIGSTOP to all backend servers if one dies\n"));
+ printf(_(" -T send SIGSTOP to all backend processes if one dies\n"));
printf(_(" -W NUM wait NUM seconds to allow attach from a debugger\n"));
printf(_("\nOptions for single-user mode:\n"));
diff --git a/src/test/examples/testlibpq4.c b/src/test/examples/testlibpq4.c
index dafc6ae..0ec0431 100644
--- a/src/test/examples/testlibpq4.c
+++ b/src/test/examples/testlibpq4.c
@@ -72,11 +72,11 @@ main(int argc, char **argv)
* defaults by looking up environment variables or, failing that, using
* hardwired constants
*/
- pghost = NULL; /* host name of the backend server */
- pgport = NULL; /* port of the backend server */
+ pghost = NULL; /* host name of the backend */
+ pgport = NULL; /* port of the backend */
pgoptions = NULL; /* special options to start up the backend
* server */
- pgtty = NULL; /* debugging tty for the backend server */
+ pgtty = NULL; /* debugging tty for the backend */
/* make a connection to the database */
conn1 = PQsetdb(pghost, pgport, pgoptions, pgtty, dbName1);
* Re: "Backend server" term usage
@ 2011-03-11 15:00 Alvaro Herrera <alvherre@commandprompt.com>
parent: Bruce Momjian <bruce@momjian.us>
1 sibling, 1 reply; 5+ messages in thread
From: Alvaro Herrera @ 2011-03-11 15:00 UTC (permalink / raw)
To: Bruce Momjian <bruce@momjian.us>; +Cc: Dmitriy Igrishin <dmitigr@gmail.com>; Robert Haas <robertmhaas@gmail.com>; pgsql-docs
Excerpts from Bruce Momjian's message of vie mar 11 11:42:58 -0300 2011:
> Alvaro Herrera wrote:
> > Excerpts from Dmitriy Igrishin's message of dom feb 20 06:19:19 -0300 2011:
> >
> > > Better, undoubtedly.
> > > Another alternative is just "server". Why? Well, for consistency, e.g. with
> > > http://www.postgresql.org/docs/9.0/static/errcodes-appendix.html
> > > Here you may see phrase "All messages emitted by the PostgreSQL server ..."
> > > and furthermore, there are some SQL standard's "SQLSTATE" code
> > > which name includes "server" rather than "backend":
> > > SQLSERVER REJECTED ESTABLISHMENT OF SQLCONNECTION
> > > But anyway, phrase "backend server" is incorrect.
> >
> > Maybe some cleanup would be good, but in that case please provide a
> > specific patch. The replacement suggested in the email that started
> > this thread seems OK, but wholesale replacement of the phrase "backend
> > server" with something else is likely to introduce as many mistakes as
> > it would fix. For example, the description of postgres' -T switch would
> > then be wrong.
> >
> > I think using the protocol chapter as reference for terms to use is a
> > bad idea -- it's one of the most obscure chapters in the documentation.
>
> OK, attached is my proposed patch; it mostly changes "backend server"
> to "backend process".
Looks good to me, thanks for the effort.
This whole thread makes me think that we should consider having a
glossary of terms in the docs.
--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: "Backend server" term usage
@ 2011-03-11 15:17 Dmitriy Igrishin <dmitigr@gmail.com>
parent: Alvaro Herrera <alvherre@commandprompt.com>
0 siblings, 1 reply; 5+ messages in thread
From: Dmitriy Igrishin @ 2011-03-11 15:17 UTC (permalink / raw)
To: Alvaro Herrera <alvherre@commandprompt.com>; +Cc: Bruce Momjian <bruce@momjian.us>; Robert Haas <robertmhaas@gmail.com>; pgsql-docs
2011/3/11 Alvaro Herrera <alvherre@commandprompt.com>
> Excerpts from Bruce Momjian's message of vie mar 11 11:42:58 -0300 2011:
> > Alvaro Herrera wrote:
> > > Excerpts from Dmitriy Igrishin's message of dom feb 20 06:19:19 -0300
> 2011:
> > >
> > > > Better, undoubtedly.
> > > > Another alternative is just "server". Why? Well, for consistency,
> e.g. with
> > > > http://www.postgresql.org/docs/9.0/static/errcodes-appendix.html
> > > > Here you may see phrase "All messages emitted by the PostgreSQL
> server ..."
> > > > and furthermore, there are some SQL standard's "SQLSTATE" code
> > > > which name includes "server" rather than "backend":
> > > > SQLSERVER REJECTED ESTABLISHMENT OF SQLCONNECTION
> > > > But anyway, phrase "backend server" is incorrect.
> > >
> > > Maybe some cleanup would be good, but in that case please provide a
> > > specific patch. The replacement suggested in the email that started
> > > this thread seems OK, but wholesale replacement of the phrase "backend
> > > server" with something else is likely to introduce as many mistakes as
> > > it would fix. For example, the description of postgres' -T switch
> would
> > > then be wrong.
> > >
> > > I think using the protocol chapter as reference for terms to use is a
> > > bad idea -- it's one of the most obscure chapters in the documentation.
> >
> > OK, attached is my proposed patch; it mostly changes "backend server"
> > to "backend process".
>
> Looks good to me, thanks for the effort.
>
> This whole thread makes me think that we should consider having a
> glossary of terms in the docs.
>
+1.
>
> --
> Álvaro Herrera <alvherre@commandprompt.com>
> The PostgreSQL Company - Command Prompt, Inc.
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>
> --
> Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-docs
>
--
// Dmitriy.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: "Backend server" term usage
@ 2011-03-11 15:21 Dmitriy Igrishin <dmitigr@gmail.com>
parent: Dmitriy Igrishin <dmitigr@gmail.com>
0 siblings, 0 replies; 5+ messages in thread
From: Dmitriy Igrishin @ 2011-03-11 15:21 UTC (permalink / raw)
To: Alvaro Herrera <alvherre@commandprompt.com>; +Cc: Bruce Momjian <bruce@momjian.us>; Robert Haas <robertmhaas@gmail.com>; pgsql-docs
2011/3/11 Dmitriy Igrishin <dmitigr@gmail.com>
>
>
> 2011/3/11 Alvaro Herrera <alvherre@commandprompt.com>
>
> Excerpts from Bruce Momjian's message of vie mar 11 11:42:58 -0300 2011:
>> > Alvaro Herrera wrote:
>> > > Excerpts from Dmitriy Igrishin's message of dom feb 20 06:19:19 -0300
>> 2011:
>> > >
>> > > > Better, undoubtedly.
>> > > > Another alternative is just "server". Why? Well, for consistency,
>> e.g. with
>> > > > http://www.postgresql.org/docs/9.0/static/errcodes-appendix.html
>> > > > Here you may see phrase "All messages emitted by the PostgreSQL
>> server ..."
>> > > > and furthermore, there are some SQL standard's "SQLSTATE" code
>> > > > which name includes "server" rather than "backend":
>> > > > SQLSERVER REJECTED ESTABLISHMENT OF SQLCONNECTION
>> > > > But anyway, phrase "backend server" is incorrect.
>> > >
>> > > Maybe some cleanup would be good, but in that case please provide a
>> > > specific patch. The replacement suggested in the email that started
>> > > this thread seems OK, but wholesale replacement of the phrase "backend
>> > > server" with something else is likely to introduce as many mistakes as
>> > > it would fix. For example, the description of postgres' -T switch
>> would
>> > > then be wrong.
>> > >
>> > > I think using the protocol chapter as reference for terms to use is a
>> > > bad idea -- it's one of the most obscure chapters in the
>> documentation.
>> >
>> > OK, attached is my proposed patch; it mostly changes "backend server"
>> > to "backend process".
>>
>> Looks good to me, thanks for the effort.
>>
>> This whole thread makes me think that we should consider having a
>> glossary of terms in the docs.
>>
> +1.
>
The implementation of this idea can be very helpful especially
for people making translations of the documentation.
>
>> --
>>
>> Álvaro Herrera <alvherre@commandprompt.com>
>> The PostgreSQL Company - Command Prompt, Inc.
>> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>>
>> --
>> Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-docs
>>
>
>
>
> --
> // Dmitriy.
>
>
>
--
// Dmitriy.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: "Backend server" term usage
@ 2011-03-12 15:18 Bruce Momjian <bruce@momjian.us>
parent: Bruce Momjian <bruce@momjian.us>
1 sibling, 0 replies; 5+ messages in thread
From: Bruce Momjian @ 2011-03-12 15:18 UTC (permalink / raw)
To: Bruce Momjian <bruce@momjian.us>; +Cc: Alvaro Herrera <alvherre@commandprompt.com>; Dmitriy Igrishin <dmitigr@gmail.com>; Robert Haas <robertmhaas@gmail.com>; pgsql-docs
Applied.
---------------------------------------------------------------------------
Bruce Momjian wrote:
> Alvaro Herrera wrote:
> > Excerpts from Dmitriy Igrishin's message of dom feb 20 06:19:19 -0300 2011:
> >
> > > Better, undoubtedly.
> > > Another alternative is just "server". Why? Well, for consistency, e.g. with
> > > http://www.postgresql.org/docs/9.0/static/errcodes-appendix.html
> > > Here you may see phrase "All messages emitted by the PostgreSQL server ..."
> > > and furthermore, there are some SQL standard's "SQLSTATE" code
> > > which name includes "server" rather than "backend":
> > > SQLSERVER REJECTED ESTABLISHMENT OF SQLCONNECTION
> > > But anyway, phrase "backend server" is incorrect.
> >
> > Maybe some cleanup would be good, but in that case please provide a
> > specific patch. The replacement suggested in the email that started
> > this thread seems OK, but wholesale replacement of the phrase "backend
> > server" with something else is likely to introduce as many mistakes as
> > it would fix. For example, the description of postgres' -T switch would
> > then be wrong.
> >
> > I think using the protocol chapter as reference for terms to use is a
> > bad idea -- it's one of the most obscure chapters in the documentation.
>
> OK, attached is my proposed patch; it mostly changes "backend server"
> to "backend process".
>
> --
> Bruce Momjian <bruce@momjian.us> http://momjian.us
> EnterpriseDB http://enterprisedb.com
>
> + It's impossible for everything to be true. +
[ text/x-diff is unsupported, treating like TEXT/PLAIN ]
> diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
> index 59b4011..1c223cb 100644
> --- a/doc/src/sgml/libpq.sgml
> +++ b/doc/src/sgml/libpq.sgml
> @@ -1612,7 +1612,7 @@ int PQsocket(const PGconn *conn);
> <para>
> Returns the process <acronym>ID</acronym>
> (PID)<indexterm><primary>PID</><secondary>determining PID of
> - server process</><tertiary>in libpq</></> of the backend server
> + server process</><tertiary>in libpq</></> of the backend
> process handling this connection.
>
> <synopsis>
> diff --git a/doc/src/sgml/problems.sgml b/doc/src/sgml/problems.sgml
> index a65baa3..3f79c6e 100644
> --- a/doc/src/sgml/problems.sgml
> +++ b/doc/src/sgml/problems.sgml
> @@ -78,7 +78,7 @@
> </listitem>
> </itemizedlist>
>
> - Here <quote>program</quote> refers to any executable, not only the backend server.
> + Here <quote>program</quote> refers to any executable, not only the backend process.
> </para>
>
> <para>
> @@ -280,9 +280,9 @@
> When writing a bug report, please avoid confusing terminology.
> The software package in total is called <quote>PostgreSQL</quote>,
> sometimes <quote>Postgres</quote> for short. If you
> - are specifically talking about the backend server, mention that, do not
> + are specifically talking about the backend process, mention that, do not
> just say <quote>PostgreSQL crashes</quote>. A crash of a single
> - backend server process is quite different from crash of the parent
> + backend process is quite different from crash of the parent
> <quote>postgres</> process; please don't say <quote>the server
> crashed</> when you mean a single backend process went down, nor vice versa.
> Also, client programs such as the interactive frontend <quote><application>psql</application></quote>
> diff --git a/doc/src/sgml/query.sgml b/doc/src/sgml/query.sgml
> index 681d08a..f4fbf11 100644
> --- a/doc/src/sgml/query.sgml
> +++ b/doc/src/sgml/query.sgml
> @@ -264,8 +264,8 @@ INSERT INTO weather (date, city, temp_hi, temp_lo)
> COPY weather FROM '/home/user/weather.txt';
> </programlisting>
>
> - where the file name for the source file must be available to the
> - backend server machine, not the client, since the backend server
> + where the file name for the source file must be available on the
> + machine running the backend process, not the client, since the backend process
> reads the file directly. You can read more about the
> <command>COPY</command> command in <xref linkend="sql-copy">.
> </para>
> diff --git a/doc/src/sgml/ref/pg_ctl-ref.sgml b/doc/src/sgml/ref/pg_ctl-ref.sgml
> index 608749f..626ed1f 100644
> --- a/doc/src/sgml/ref/pg_ctl-ref.sgml
> +++ b/doc/src/sgml/ref/pg_ctl-ref.sgml
> @@ -134,7 +134,7 @@ PostgreSQL documentation
> <application>pg_ctl</application> is a utility for initializing a
> <productname>PostgreSQL</productname> database cluster, starting,
> stopping, or restarting the <productname>PostgreSQL</productname>
> - backend server (<xref linkend="app-postgres">), or displaying the
> + database server (<xref linkend="app-postgres">), or displaying the
> status of a running server. Although the server can be started
> manually, <application>pg_ctl</application> encapsulates tasks such
> as redirecting log output and properly detaching from the terminal
> diff --git a/src/backend/libpq/pqsignal.c b/src/backend/libpq/pqsignal.c
> index 31e37e9..0fee280 100644
> --- a/src/backend/libpq/pqsignal.c
> +++ b/src/backend/libpq/pqsignal.c
> @@ -22,7 +22,7 @@
> * how to handle signalling.
> *
> * signal(2) handling - this is here because it affects some of
> - * the frontend commands as well as the backend server.
> + * the frontend commands as well as the backend processes.
> *
> * Ultrix and SunOS provide BSD signal(2) semantics by default.
> *
> diff --git a/src/backend/main/main.c b/src/backend/main/main.c
> index 5d07788..43d182b 100644
> --- a/src/backend/main/main.c
> +++ b/src/backend/main/main.c
> @@ -310,7 +310,7 @@ help(const char *progname)
> printf(_(" -O allow system table structure changes\n"));
> printf(_(" -P disable system indexes\n"));
> printf(_(" -t pa|pl|ex show timings after each query\n"));
> - printf(_(" -T send SIGSTOP to all backend servers if one dies\n"));
> + printf(_(" -T send SIGSTOP to all backend processes if one dies\n"));
> printf(_(" -W NUM wait NUM seconds to allow attach from a debugger\n"));
>
> printf(_("\nOptions for single-user mode:\n"));
> diff --git a/src/test/examples/testlibpq4.c b/src/test/examples/testlibpq4.c
> index dafc6ae..0ec0431 100644
> --- a/src/test/examples/testlibpq4.c
> +++ b/src/test/examples/testlibpq4.c
> @@ -72,11 +72,11 @@ main(int argc, char **argv)
> * defaults by looking up environment variables or, failing that, using
> * hardwired constants
> */
> - pghost = NULL; /* host name of the backend server */
> - pgport = NULL; /* port of the backend server */
> + pghost = NULL; /* host name of the backend */
> + pgport = NULL; /* port of the backend */
> pgoptions = NULL; /* special options to start up the backend
> * server */
> - pgtty = NULL; /* debugging tty for the backend server */
> + pgtty = NULL; /* debugging tty for the backend */
>
> /* make a connection to the database */
> conn1 = PQsetdb(pghost, pgport, pgoptions, pgtty, dbName1);
>
> --
> Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-docs
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2011-03-12 15:18 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2011-03-11 14:42 "Backend server" term usage Bruce Momjian <bruce@momjian.us>
2011-03-11 15:00 ` Alvaro Herrera <alvherre@commandprompt.com>
2011-03-11 15:17 ` Dmitriy Igrishin <dmitigr@gmail.com>
2011-03-11 15:21 ` Dmitriy Igrishin <dmitigr@gmail.com>
2011-03-12 15:18 ` Bruce Momjian <bruce@momjian.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox