single-user vs standalone in docs and messages

Lists: pgsql-hackers
From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: single-user vs standalone in docs and messages
Date: 2013-06-13 22:10:28
Message-ID: CAMkU=1x=sasRuP+9CChjcHNS0=U4pwvQGe5f4ycdWoQm9tKfqA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Some places in the docs and elog hints refer to "standalone" backends,
while the official name as used in app-postgres.html is "single-user mode",
and in fact "standalone" does not appear on that page.

This tries to standardize the other locations to use "single-user". I
think I did the right thing with the message translation files, but I can't
figure out how to test that.

I made no attempt to change code-comments, just the user-facing parts.

Cheers,

Jeff

Attachment Content-Type Size
standalone_single_user_v1.patch application/octet-stream 13.1 KB
From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: single-user vs standalone in docs and messages
Date: 2013-06-13 22:18:35
Message-ID: 20130613221835.GQ5491@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Jeff Janes escribió:

> I think I did the right thing with the message translation files, but
> I can't figure out how to test that.

Don't do that. These files are automatically generated. Just leave
them alone and translators will get to them in time.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: single-user vs standalone in docs and messages
Date: 2013-06-14 22:30:22
Message-ID: CA+TgmoY54kjDOVVZ25Oh8WO8xmqnT-mKzW2tyMDB51o1w0S3eQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Thu, Jun 13, 2013 at 6:10 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> Some places in the docs and elog hints refer to "standalone" backends, while
> the official name as used in app-postgres.html is "single-user mode", and in
> fact "standalone" does not appear on that page.
>
> This tries to standardize the other locations to use "single-user". I think
> I did the right thing with the message translation files, but I can't figure
> out how to test that.
>
> I made no attempt to change code-comments, just the user-facing parts.

I think you could tell people to use "single-user mode" instead of "a
standalone backend", but telling them to use "a single-user backend"
just seems weird.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: single-user vs standalone in docs and messages
Date: 2013-06-21 03:10:14
Message-ID: 1371784214.8108.0.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Thu, 2013-06-13 at 15:10 -0700, Jeff Janes wrote:
> Some places in the docs and elog hints refer to "standalone" backends,
> while the official name as used in app-postgres.html is "single-user
> mode",
> and in fact "standalone" does not appear on that page.
>
> This tries to standardize the other locations to use "single-user". I
> think I did the right thing with the message translation files, but I
> can't
> figure out how to test that.
>
> I made no attempt to change code-comments, just the user-facing
> parts.

committed with some adjustments