From: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
---|---|
To: | Lew <lew(at)nospam(dot)lewscanon(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Multiple customers sharing one database? |
Date: | 2007-06-03 22:06:22 |
Message-ID: | 11AF6096-D881-46DA-A8A7-1CCFB3C727F2@seespotcode.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Jun 3, 2007, at 12:45 , Lew wrote:
> Michael Glaesemann wrote:
>
>> Unless the database schema is shared by the different customers,
>> I'd set up a separate database for each. There's better security
>> with separate databases, and since different customer's data would
>> never be combined, there's no advantage to putting them in the
>> same one. Per database overhead is probably going to be negligible
>> compared to the infrastructure you'd want to put in place for
>> security.
>
> I am always confused by the overloaded term "database" in such
> discussions. Do we mean the RDBMS engine, i.e., run separate
> instances of PG? I sure would recommend against that. Or do we
> mean it as the PG documentation does, e.g.,
> <http://www.postgresql.org/docs/8.1/interactive/ddl-schemas.html>
I likewise try to be careful in my usage of database and database
server as they are different things. I meant (and used) database, not
database server.
Michael Glaesemann
grzm seespotcode net
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Moran | 2007-06-03 22:08:01 | Re: collision in serial numbers after INSERT? |
Previous Message | Scott Ribe | 2007-06-03 21:46:04 | Re: Corruption of files in PostgreSQL |