From: | "Christopher Nelson" <paradox(at)BBHC(dot)ORG> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | PostgreSQL as a filesystem |
Date: | 2005-04-18 20:42:40 |
Message-ID: | 79A4CBFE19FBA8428782AA6B5E64E27802804CB3@server3.bbhclan.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
This isn't a high-priority question.
I'm developing a hobby OS and I'm looking into file systems. I've
thought about writing my own, and that appeals, but I'm also very
interested in the database-as-a-filesystem paradigm. It would be nice
to not have to write all of the stuff that goes into the DBMS (e.g.
parsers, query schedulers, etc) myself.
So I was wondering what sort of filesystem requirements Postgre has.
For example, could I write a simple interface layer that just requests
blocks from the physical device and translate those into byte sets, or
does the DB actually require multiple files mapped by a larger file
system that maintains names, etc.
I guess my real question is how much file system support is really
required by the DBMS's disk routines. Please reply to
nadiasvertex(at)gmail(dot)com since I'm not subscribed to this list. Thanks in
advance!
-={C}=-
From | Date | Subject | |
---|---|---|---|
Next Message | Relyea, Mike | 2005-04-18 21:02:31 | Re: Plpgsql function with unknown number of args |
Previous Message | Philip Hallstrom | 2005-04-18 20:41:41 | Re: tsearch2 |