From: Tom Lane <tgl@sss.pgh.pa.us>
To: scott.marlowe <scott.marlowe@ihs.com>
Cc: Jim C. Nasby <jim@nasby.net>
Cc: Matthew Nuzum <cobalt@bearfruit.org>
Cc: 'Josh Berkus' <josh@agliodbs.com>
Cc: 'Pgsql-Performance' <pgsql-performance@postgresql.org>
Subject: Re: choosing the right platform
Date: Thu, 10 Apr 2003 13:17:39 -0400
Message-ID: <5112.1049995059@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.33.0304101042480.23398-100000@css120.ihs.com>
References: <Pine.LNX.4.33.0304101042480.23398-100000@css120.ihs.com>
"scott.marlowe" <scott.marlowe@ihs.com> writes:
> Note that this is a good thing (TM) since it frees the postgresql
> development team to do other things than worry about caching 1 gig of
> data.
Yeah. I think this is one very fundamental difference of design
philosophy between Postgres and more-traditional databases such as
Oracle. We prefer to let the kernel and filesystem do their jobs,
and we assume they will do them well; whereas Oracle wants to bypass
if not replace the kernel and filesystem. Partly this is a matter of
the PG project not having the manpower to replace those layers. But
I believe the world has changed in the last twenty years, and the Oracle
approach is now obsolete: it's now costing them design and maintenance
effort that isn't providing much return. Modern kernels and filesystems
are *good*, and it's not easy to do better. We should focus our efforts
on functionality that doesn't just duplicate what the OS can do.
This design approach shows up in other areas too. For instance, in
another thread I was just pointing out that there is no need for our
frontend/backend protocol to solve communication problems like dropped
or duplicated packets; TCP does that perfectly well already.
regards, tom lane
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-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, scott.marlowe@ihs.com, jim@nasby.net, cobalt@bearfruit.org, josh@agliodbs.com
Subject: Re: choosing the right platform
In-Reply-To: <5112.1049995059@sss.pgh.pa.us>
References: <Pine.LNX.4.33.0304101042480.23398-100000@css120.ihs.com> <5112.1049995059@sss.pgh.pa.us>
* 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