Content-Type: text/plain; charset=UTF-8
Cc: Bruce Momjian <bruce@momjian.us>, Robert Haas <robertmhaas@gmail.com>,
	pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: Terms.
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Dmitriy Igrishin <dmitigr@gmail.com>
In-reply-to: <AANLkTi=0h=Y-7=2vLZx6QYZvHRe-GiAqGBgHJe2bL4Nh@mail.gmail.com>
References: <1285091969-sup-850@alvh.no-ip.org>
	<201102200133.p1K1XNO24266@momjian.us>
	<AANLkTi=0h=Y-7=2vLZx6QYZvHRe-GiAqGBgHJe2bL4Nh@mail.gmail.com>
Date: Mon, 21 Feb 2011 14:07:34 -0300
Message-Id: <1298307429-sup-8882@alvh.no-ip.org>
User-Agent: Sup/git
Content-Transfer-Encoding: 8bit

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.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support