Re: [GENERAL] schema or database
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 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
Re: [GENERAL] schema or database
Thanks for your suggestion. I'd like to use schema as you suggest. yours, michael On Mon, 13 Apr 2015 11:20:59 +0900 Ian Barwick wrote: > On 13/04/15 11:08, Michael Cheung wrote: > > hi, all; > > > > I am new here. And I need some suggestion. > > > > I have many similar database to store data for every customer. > > Structure of database is almost the same. > > As I use same application to control all these data, so I can only use > > one database user to connect to these database. > > And I have no needs to query table for different customer together. > > > > I wonder which I should use, different shema or different database to store > > data? > > > > I 'd like to know the advantage and disadvantage for using schema or > > database. > > 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. > > > Regards > > Ian Barwick > > -- > Ian Barwick http://www.2ndQuadrant.com/ > PostgreSQL Development, 24x7 Support, Training & Services > > > -- > 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
[GENERAL] schema or database
hi, all; I am new here. And I need some suggestion. I have many similar database to store data for every customer. Structure of database is almost the same. As I use same application to control all these data, so I can only use one database user to connect to these database. And I have no needs to query table for different customer together. I wonder which I should use, different shema or different database to store data? I 'd like to know the advantage and disadvantage for using schema or database. Thanks michael -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
