From: Alvaro Herrera <alvherre@commandprompt.com>
To: Dmitriy Igrishin <dmitigr@gmail.com>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: Terms.
Date: Tue, 21 Sep 2010 14:01:13 -0400
Message-ID: <1285091969-sup-850@alvh.no-ip.org> (raw)
In-Reply-To: <AANLkTim0cNwEd-T-+G9cFekV7PvuxowjW7SzD0k8oc-t@mail.gmail.com>
References: <AANLkTin2wu81c_TfQijqU=CGH=fFF+1g-LF=ArQopCsy@mail.gmail.com>
<201009201529.o8KFTLQ18950@momjian.us>
<AANLkTim0cNwEd-T-+G9cFekV7PvuxowjW7SzD0k8oc-t@mail.gmail.com>
Excerpts from Dmitriy Igrishin's message of lun sep 20 15:52:43 -0400 2010:
> Hey Bruce,
>
> Its interesting indeed, because I always wanted to know why libpq
> named "libpq". Thanks!
> But I wrote not about libpq functions, I just wanted to say about
> unnecessary (IMO) redundancy - the combinations of terms "backend server"
> seems to me inaccuracy.
could be, but we're already using that term elsewhere. Maybe we should
consistently use some other term.
$ git grep 'backend server'
doc/src/sgml/libpq.sgml: backend server and to receive the results of these queries.
doc/src/sgml/libpq.sgml: <productname>PostgreSQL</productname> backend server. An
doc/src/sgml/libpq.sgml: server process</><tertiary>in libpq</></> of the backend server
doc/src/sgml/problems.sgml: Here <quote>program</quote> refers to any executable, not only the backend server.
doc/src/sgml/problems.sgml: are specifically talking about the backend server, mention that, do not
doc/src/sgml/problems.sgml: backend server process is quite different from crash of the parent
doc/src/sgml/query.sgml: backend server machine, not the client, since the backend server
doc/src/sgml/ref/pg_ctl-ref.sgml: backend server (<xref linkend="app-postgres">), or displaying the
src/backend/libpq/pqsignal.c: * the frontend commands as well as the backend server.
src/backend/main/main.c: printf(_(" -T send SIGSTOP to all backend servers if one dies\n"));
src/backend/po/de.po:msgid " -T send SIGSTOP to all backend servers if one dies\n"
src/backend/po/es.po:msgid " -T send SIGSTOP to all backend servers if one dies\n"
src/backend/po/fr.po:msgid " -T send SIGSTOP to all backend servers if one dies\n"
src/backend/po/ja.po:msgid " -T send SIGSTOP to all backend servers if one dies\n"
src/backend/po/pt_BR.po:msgid " -T send SIGSTOP to all backend servers if one dies\n"
src/backend/po/tr.po:msgid " -T send SIGSTOP to all backend servers if one dies\n"
src/bin/psql/settings.h: int sversion; /* backend server version */
src/test/examples/testlibpq4.c: pghost = NULL; /* host name of the backend server */
src/test/examples/testlibpq4.c: pgport = NULL; /* port of the backend server */
src/test/examples/testlibpq4.c: pgtty = NULL; /* debugging tty for the backend server */
--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
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: alvherre@commandprompt.com, dmitigr@gmail.com, bruce@momjian.us, robertmhaas@gmail.com
Subject: Re: Terms.
In-Reply-To: <1285091969-sup-850@alvh.no-ip.org>
* 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