Re: Terms.

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Dmitriy Igrishin <dmitigr(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: Terms.
Date: 2011-02-20 01:33:23
Message-ID: 201102200133.p1K1XNO24266@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Alvaro Herrera wrote:
> 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 */

Any ideas on this? Is "backend" better than "backend server"?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

  • Re: Terms. at 2010-09-21 18:01:13 from Alvaro Herrera

Responses

  • Re: Terms. at 2011-02-20 09:19:19 from Dmitriy Igrishin

Browse pgsql-docs by date

  From Date Subject
Next Message Fabien COELHO 2011-02-20 07:48:21 Re: [BUGS] issue about information_schema REFERENTIAL_CONSTRAINTS
Previous Message Bruce Momjian 2011-02-20 00:11:01 Re: [BUGS] issue about information_schema REFERENTIAL_CONSTRAINTS