>Restricting users to a specific schema is possible and practical. If you
>want have each website use a different database user. You can even
>change their search_path to use that schema by default.
>
>  
>
Ok. Do you have more information, or a link to such a setup ?
(But note that with different databases, I can get a higher level of 
security, restricting
access to users before they connect to any database, with "pg_hba.conf".)

>>  - error tolerance/independance (to not put all my eggs in the same 
>>basket, or "in the same cluster" !)
>>    
>>
>
>Unless you intend to use physically separate PostgreSQL daemons
>operating on different ports, you have the same problem with both
>configurations.
>  
>
I was thinking about the eventual corruption of a database, not of 
PostgreSQL.
If a database happens to be corrupted, only this one need failover. In 
the case of a huge database,
everything is concerned by the failure (and by the failover procedure 
!), which is a *pain*...

>>  - scalability (for example, if I want to migrate *one* database from 
>>one server to another...)
>>    
>>
>
>Assuming the schemas are used independently, this would not impact them
>in the least. Dump a specific schema and move it to another server if
>necessary.
>  
>
I was thinking about moving one database to another server using Slony, 
in order to cut down the
maintenance time. Instead, if I have to dump a schema, I can't use 
Slony, and I need to lock access
to this schema for a very long time (because WAN)...

I'm still open to any advice !

Thank you,
Philippe Ferreira,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://gborg.postgresql.org/pipermail/slony1-general/attachments/20051101/3baa7b48/attachment.html