Re: PG vs MySQL

From: Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my>
To: (Mike Nolan <nolan(at)gw(dot)tssi(dot)com>, scrappy(at)postgresql(dot)org (Marc G(dot) Fournier))
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: PG vs MySQL
Date: 2004-03-30 13:26:25
Message-ID: 5.2.1.1.1.20040330212112.0339c7c0@mbox.jaring.my
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

At 06:16 PM 3/29/2004 -0600, Mike Nolan wrote:

> > Now, that doesn't preclude clients from seeing the names of another
> > clients database using \l, but unless there is gross mis-management of the
> > pg_hba.conf, seeing the names of other databases doesn't give other
> > clients any benefits ...
>
>That rather depends upon what those clients are doing, doesn't it?
>
>I can see benefits from being able to completely isolate one client/database
>from another, even to the point of not giving them any hints that they're
>sharing the same database server. (Depending on how fanatical I am about
>it, there are other solutions, such as separate instances or completely
>separate physical systems, but those present a different set of
>administrative issues.)

It would just be better to run separate postgres instances.

The resources used may be higher, but the isolation is better.

If RAM was cheaper I'd give each customer their own virtual machine.

Regards,
Link.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Marc G. Fournier 2004-03-30 14:13:26 Re: Best open source db poll currently
Previous Message Robert Treat 2004-03-30 13:22:27 Re: Best open source db poll currently