| From: | Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: smgr.c and smgrtype.c |
| Date: | 2004-10-19 09:02:59 |
| Message-ID: | 4174D843.8040305@nttdata.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>I'm trying to modify the storage manager now.
>
> Um ... why?
Because I want to add my new storage manager.
It is not just for (single) magnetic disk.
> If anyone had wanted to add a new storage manager in the last fifteen
> years, we'd doubtless have tried to clean this up some, but no one has
> and I'm not really expecting anyone to try in the next fifteen...
I guess clean separation and APIs are necessary for now.
If one need to modify/extend a storage manager for better performance,
clean design and APIs are essentials.
For my purpose, I'm thinking about a pluggable storage manager
mechanism using dynamic loading, because I want to develop
my smgr independently from main codebase...
--
NAGAYASU Satoshi <nagayasus(at)nttdata(dot)co(dot)jp>
OpenSource Development Center,
NTT DATA Corp. http://www.nttdata.co.jp/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tham Paudel | 2004-10-19 11:39:40 | Managing Directories |
| Previous Message | Tom Lane | 2004-10-19 07:27:56 | Re: smgr.c and smgrtype.c |