From: | David Garamond <lists(at)zara(dot)6(dot)isreserved(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: EMBEDDED PostgreSQL |
Date: | 2005-01-25 23:15:42 |
Message-ID: | 41F6D31E.2050907@zara.6.isreserved.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Richard_D_Levine(at)raytheon(dot)com wrote:
> The trick is making database administration invisible to the user. Since
> Firebird requires no administration, it's easy. The single file database
> architecture in Firebird is also easy since you generally have only one
> drive.
The decision not to create an embedded Postgres version is never about
administration issue. If we want to, we can make Postgres administration
and configuration as minimum as possible by creating, say, a pg_autotune
daemon that monitors the OS, db activity, and usage pattern, and
automatically adjusts the kernel and/or db parameters. I think there's
something like this in Oracle 10g and perhaps someday there will be too
in Postgres.
It's about reliability. Running the app and dbms in the same process
space will not guarantee that bugs in app will not mess up the database.
And after all, the "Firebird requires no administration" statement is
more of a marketing gimmick anyway. Is it really 100% DBA-free? Can
Firebird automatically connect to newegg.com and buy an extra harddisk
if it runs out of disk space? :-)
To me Postgres is already pretty low in administrative demand as it is.
Not that it cannot be improved, of course.
--
dave
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2005-01-25 23:21:08 | Re: Problem with Postgres V 8 and DBI maybe |
Previous Message | Dann Corbit | 2005-01-25 23:07:28 | Re: visualizing B-tree index coverage |