From: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
---|---|
To: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> |
Cc: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: postgres-9.1beta3 typo: recommendable --> recommended |
Date: | 2011-08-02 04:53:25 |
Message-ID: | CAJKUy5gT=YtAnOzMy7eXXzwvjYvycE94f4VsM7+uG1iJiT+Vuw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Fri, Jul 29, 2011 at 1:42 AM, Gavin Flower
<GavinFlower(at)archidevsys(dot)co(dot)nz> wrote:
> /postgres-9.1/share/doc/html/manage-ag-overview.html
> In the folowing partagrasoh 'recommendable' should be 'recommended'.
>
> [...]
> Databases are physically separated and access
> control is managed at the connection level. If one PostgreSQL server
> instance is to house projects or users that should be separate and for the
> most part unaware of each other, it is therefore recommendable to put them
> into separate databases. If the projects or users are interrelated and
> should be able to use each other's resources, they should be put in the same
> database but possibly into separate schemas.
> [...]
>
maybe it's because i'm not a natural english speaker but this sounds
like we are recommended to put the users in another database. probably
it is refering to the user's resources... maybe we can make it more
explicit?
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
From | Date | Subject | |
---|---|---|---|
Next Message | francisco natera | 2011-08-10 16:56:40 | DOCUMENTATION IN OTHERS IDIOMS |
Previous Message | Peter Eisentraut | 2011-07-29 20:40:04 | XML man page rendering issue |