From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Christophe <xof(at)thebuild(dot)com> |
Cc: | "Postgres General List" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Oracle and Postgresql |
Date: | 2008-09-15 21:40:01 |
Message-ID: | dcc563d10809151440n2652539fs6461f7a0a1a1231e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-www |
On Mon, Sep 15, 2008 at 3:29 PM, Christophe <xof(at)thebuild(dot)com> wrote:
>
> On Sep 15, 2008, at 1:15 PM, Scott Marlowe wrote:
>> But whether it's oracle or postgresql, this is just security through
>> obscurity. If you have root access on the server either method would
>> be trivial to hack.
>
> Oh, sure. (Same is true of Oracle, of course.) I wouldn't use it myself,
> but if this is a feature-checkbox item, that's how you'd need to go about
> doing it.
But as long as there is real progress to be made elsewhere, I'd rather
the hackers use their efforts there. I'm not such a big fan of
checkboxes, and tend to look under the hood at what was done to make
the checkbox work. Like MySQL has built in replication. Sure, it's
not suitable for a large percentage of uses, is unreliable, and prone
to silent failure, but they got the box checked for it.
The problem is that people often assume that once the box is checked
they don't need to go / look any farther. I'd rather have postgresql's
slightly confusing but huge choice in replication engines than the one
in mysql that's limited and unreliable.
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Langhoff | 2008-09-15 21:43:30 | Re: Pg 8.3 tuning recommendations for embedded low-memory device (for OLPC :-) ) |
Previous Message | Matt Magoffin | 2008-09-15 21:32:41 | Re: Out of memory on SELECT (from sort?) in 8.3 |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2008-09-15 22:55:07 | Re: Oracle and Postgresql |
Previous Message | Christophe | 2008-09-15 21:29:37 | Re: Oracle and Postgresql |