Ok. Do you have more information, or a link to such a setup ?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. (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".) 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... 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, |
_______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
