Re: [cobalt-users] install second copy of postgresql on raq4

["Steve Werby" <steve-lists@xxxxxxxxxxxx>]

"Chris Demain" <cdemain@xxxxxxxxxxx> wrote:
> I can't even begin to imagine why you would want to do this.
> PostgreSQL supports multiple users, multiple databases, and has very
> fine-grain ACL capability.
>
> A second install for a second database?  A needless waste of CPU cycles,
in
> my ever so humble opinion.

Of course, you're right that it's overkill for most situations, but offhand
I can think of  several reasons why someone might want to install a second
PostgreSQL.

In order to use a different version of PostgreSQL.  7.0.2 is pre-installed
on the RaQ4.  7.1.3 is the latest version.  You may want to test a newer
version or may have a client who needs a feature in the newer version, but
you may not be ready for the Cobalt backend and other clients to use that
version.  Or you may be concerned that a future Cobalt upgrade will
overwrite or delete your databases and configuration files.

In order to easily optimize PostgreSQL, change run-time settings, set
different debugging and logging options and tune as appropriate for each
installation.

In order to run PostgreSQL on a non-standard port.  You may have clients who
cannot access PostgreSQL because they are behind a firewall and you may wish
to allow them access via a different port.  Or you may want to run an
SSL-enabled version on a different port or keep your internal databases on a
different port with access to only your machine by creating a rule in
ipchains.

I can think of more, but I think that gives you a good example of some
situations where a second copy may be beneficial.

Sure, some of these things may be accomplished without installing a second
copy of PostgreSQL, but the solution may not be as clean or easy to manage
and the resources associated with running a second copy of PostgreSQL on a
box with decent RAM are negligible IMO.

--
Steve Werby
President, Befriend Internet Services LLC
http://www.befriend.com/