Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 3EAD21337B69 for ; Tue, 21 Sep 2010 15:01:33 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 28254-04 for ; Tue, 21 Sep 2010 18:01:26 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from spinlock.commandprompt.com (host-215.commandprompt.net [207.173.203.215]) by mail.postgresql.org (Postfix) with ESMTP id 5EDD11337B59 for ; Tue, 21 Sep 2010 15:01:24 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by spinlock.commandprompt.com (Postfix) with ESMTP id CACAA348014; Tue, 21 Sep 2010 11:01:18 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at commandprompt.com Received: from spinlock.commandprompt.com ([127.0.0.1]) by localhost (spinlock.commandprompt.com.commandprompt.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MjnlNWhBWXRQ; Tue, 21 Sep 2010 11:01:16 -0700 (PDT) Received: from perhan.alvh.no-ip.org (200-126-90-175.bk6-dsl.surnet.cl [200.126.90.175]) by spinlock.commandprompt.com (Postfix) with ESMTPSA id B197B348013; Tue, 21 Sep 2010 11:01:15 -0700 (PDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 6CD626E8AB; Tue, 21 Sep 2010 14:01:13 -0400 (CLT) Content-Type: text/plain; charset=UTF-8 Cc: Bruce Momjian , Robert Haas , pgsql-docs Subject: Re: Terms. From: Alvaro Herrera To: Dmitriy Igrishin In-reply-to: References: <201009201529.o8KFTLQ18950@momjian.us> Date: Tue, 21 Sep 2010 14:01:13 -0400 Message-Id: <1285091969-sup-850@alvh.no-ip.org> User-Agent: Sup/git Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201009/84 X-Sequence-Number: 6074 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: PostgreSQL backend server. An doc/src/sgml/libpq.sgml: server processin libpq of the backend server doc/src/sgml/problems.sgml: Here program 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 (), 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 The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support