| From: | Adrian Klaver <aklaver(at)comcast(dot)net> |
|---|---|
| To: | nadiasvertex(at)gmail(dot)com |
| Cc: | PostreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL as a filesystem |
| Date: | 2005-04-19 02:35:02 |
| Message-ID: | 200504181935.02337.aklaver@comcast.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Monday 18 April 2005 01:42 pm, Christopher Nelson wrote:
> 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}=-
You might be interested in the following site. It is a Python DBAPI driver
that uses the file system as a database.
http://fssdb.sourceforge.net/
--
Adrian Klaver
aklaver(at)comcast(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aaron Glenn | 2005-04-19 03:38:14 | Re: PostgreSQL as a filesystem |
| Previous Message | Joshua D. Drake | 2005-04-19 02:15:18 | Re: PostgreSQL as a filesystem |