From: Bruce Momjian <bruce@momjian.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Dmitriy Igrishin <dmitigr@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: "Backend server" term usage
Date: Sat, 12 Mar 2011 10:18:09 -0500 (EST)
Message-ID: <201103121518.p2CFI9J29665@momjian.us> (raw)
In-Reply-To: <201103111442.p2BEgwh02462@momjian.us>
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. +
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: bruce@momjian.us, alvherre@commandprompt.com, dmitigr@gmail.com, robertmhaas@gmail.com
Subject: Re: "Backend server" term usage
In-Reply-To: <201103121518.p2CFI9J29665@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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