Message-ID: <4E325671.8070602@archidevsys.co.nz>
Date: Fri, 29 Jul 2011 18:42:57 +1200
From: Gavin Flower <GavinFlower@archidevsys.co.nz>
Organization: ArchiDevSys
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.2.18) Gecko/20110621 Fedora/3.1.11-1.fc14
	Lightning/1.0b3pre Thunderbird/3.1.11
MIME-Version: 1.0
To: pgsql-docs@postgresql.org
Subject: postgres-9.1beta3 typo: recommendable --> recommended
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

/postgres-9.1/share/doc/html/manage-ag-overview.html
In the folowing partagrasoh 'recommendable' should be 'recommended'.

[...]
When connecting to the database server, a client must specify in its 
connection request the name of the database it wants to connect to. It 
is not possible to access more than one database per connection. 
However, an application is not restricted in the number of connections 
it opens to the same or other databases. 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. Schemas are a purely logical structure and who can access what 
is managed by the privilege system. More information about managing 
schemas is in Section 5.7.
[...]