pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Browne <cbbrowne@acm.org>
To: pgsql-general@postgresql.org
Subject: Re: Database Selection
Date: Wed, 26 Apr 2006 21:59:15 -0400
Message-ID: <87vesvdbik.fsf@wolfe.cbbrowne.com> (raw)
References: <1145863743.280424.116910@y43g2000cwc.googlegroups.com>
	<20060424230049.GH64695@pervasive.com>
	<1145944010.148139.26490@j33g2000cwa.googlegroups.com>
	<200604262111.26037.xzilla@users.sourceforge.net>

After takin a swig o' Arrakan spice grog, xzilla@users.sourceforge.net (Robert Treat) belched out:
> On Tuesday 25 April 2006 01:46, IvoD wrote:
>> My "sixth sense" tells me that PostgreSQL is better than MySQL,
>> therefore for main app I prefer PostgreSQL; but I am in doubt to
>> run only one db engine for two databases. But my "inner space"
>> tells me to separate newsgroups system and company data system and
>> run two different db engines - in light of security (although only
>> one db engine looks promissing).
>
> This seems pretty illogical if you follow that line of thinking out
> a little further.  Would you expect it to be more secure if you ran
> one system on linux, apache, mod_foo and the other on bsd, lighty,
> and mod_bar ?  Best to through your support behind one complete
> system (sounds like postgresql from previous postings) that can do
> the job and become an expert in making that system secure.

I approve of the "avoid monoculture" notion, in some ways.

After all, it *is* an enormous problem that the world is filled with
Windows systems that run the same kernels, most of the same drivers,
the same MS Office, the same Outlook, and which hence are vulnerable
to the varied array of Things That Attack Windows.

And "script kiddies" have had a history of analyzing what
vulnerabilities Red Hat left in their distribution.  A monoculture of
Red Hat 7.2 systems isn't all that secure, either.

I think we'd be in a "better world," computing-wise, if we had some
better diversity of the sort where we had a multiplicity of platforms.
MVS, VMS, OS/2, Unix, all have been been meaningful to that end.

But I'm not at all sure that security is enhanced simply in the fact
of having multiple flavours of databases in the environment.  I can
only see that being of material assistance once you have gotten to the
point where it *isn't* more useful to secure what you already have
than it is to introduce brand new components you need to learn to
secure.
-- 
let name="cbbrowne" and tld="gmail.com" in String.concat "@" [name;tld];;
http://cbbrowne.com/info/wp.html
If men  can run the world,  why can't they stop  wearing neckties? How
intelligent is it to start the day by tying a little noose around your
neck? --Linda Ellerbee



view thread (27+ messages)  latest in thread

Message-ID: <87vesvdbik.fsf@wolfe.cbbrowne.com>
Permalink:  ../87vesvdbik.fsf@wolfe.cbbrowne.com/
Also on:    postgresql.org/message-id/87vesvdbik.fsf@wolfe.cbbrowne.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: cbbrowne@acm.org
  Subject: Re: Database Selection
  In-Reply-To: <87vesvdbik.fsf@wolfe.cbbrowne.com>
  References: <1145863743.280424.116910@y43g2000cwc.googlegroups.com> <20060424230049.GH64695@pervasive.com> <1145944010.148139.26490@j33g2000cwa.googlegroups.com> <200604262111.26037.xzilla@users.sourceforge.net> <87vesvdbik.fsf@wolfe.cbbrowne.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox