From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: small smgrcreate cleanup patch |
Date: | 2010-08-20 14:20:18 |
Message-ID: | 4C6E8F22.2030208@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 20/08/10 17:01, Robert Haas wrote:
> On Fri, Aug 20, 2010 at 9:51 AM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> On 20/08/10 16:30, Robert Haas wrote:
>>>
>>> I really like the idea of trying to use network-based storage in some
>>> way. Gigabit Ethernet is a big I/O channel.
>>
>> NFS?
>
> I don't particularly trust NFS to be either reliable or performant for
> database use. Do you?
Depends on the implementation, I guess, but the point is that there's a
bazillion network-based filesystems with different tradeoffs out there
already. It seems unlikely that you could outperform them with something
built into PostgreSQL.
To put it other way, if you built network-based storage into PostgreSQL,
what PostgreSQL-specific knowledge could you take advanage of to make it
more performant/reliable? If there isn't any, I don't see the point.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-08-20 14:28:04 | Interruptible sleeps (was Re: CommitFest 2009-07: Yay, Kevin! Thanks, reviewers!) |
Previous Message | Tom Lane | 2010-08-20 14:18:31 | Re: Deadlock bug |