| From: | "Mark Cave-Ayland" <mark(dot)cave-ayland(at)siriusit(dot)co(dot)uk> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Rewriting Free Space Map |
| Date: | 2008-03-17 18:54:28 |
| Message-ID: | 64383.86.3.91.160.1205780068.squirrel@ra.siriusit.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2008-03-17 at 13:23 -0400, Tom Lane wrote:
> I'm not wedded to "forks", that's just the name that was used in the
> only previous example I've seen. Classic Mac had a "resource fork"
> and a "data fork" within each file.
>
> Don't think I like "maps" though, as (a) that prejudges what the
> alternate forks might be used for, and (b) the name fails to be
> inclusive of the data fork. Other suggestions anyone?
I believe that in the world of NTFS the concept is called "streams":
http://support.microsoft.com/kb/105763.
HTH,
Mark.
--
Mark Cave-Ayland
Sirius Corporation - The Open Source Experts
http://www.siriusit.co.uk
T: +44 870 608 0063
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-03-17 19:02:04 | Re: Rewriting Free Space Map |
| Previous Message | Jochem van Dieten | 2008-03-17 18:45:06 | Re: Rewriting Free Space Map |