| 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: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| 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 | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-06-13 22:12:05 | Re: Passing fdw_private data from PlanForeignScan to PlanForeignModify |
| Previous Message | Bernd Helmle | 2013-06-13 22:00:23 | Re: Passing fdw_private data from PlanForeignScan to PlanForeignModify |