Thanks for your additional comment. It is more clear, I'd better to using schema more than using database.
yours, michael On Sun, 12 Apr 2015 19:24:30 -0700 John R Pierce <pie...@hogranch.com> wrote: > On 4/12/2015 7:20 PM, Ian Barwick wrote: > > If as you say access to the database is via a single application database > > user, it will probably make more sense to use multiple schemas rather than > > multiple databases. Keeping everything in one database will simplify > > administration (e.g. making backups - ypu'll just need to dump the one > > database > > rather than looping through a variable number) and will make life easier if > > you > > ever need to do some kind of query involving multiple customers. > > There will also be less overhead when adding a new schema vs adding > > a new database. > > and less overhead in connections, as one client connection can serve multiple > customers > > -- john r pierce, recycling bits in santa cruz > > > > -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
