| From: | "Dawid Kuroczko" <qnex42(at)gmail(dot)com> |
|---|---|
| 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 19:34:42 |
| Message-ID: | 758d5e7f0803171234m76678d52m61aa79ea84abee84@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 17, 2008 at 6:23 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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?
Shadow? As each err, fork trails each relfilenode? (Or perhaps "shade").
Hints? As something more generic than "map"?
Regards,
Dawid
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-03-17 19:43:32 | Re: New style of hash join proposal |
| Previous Message | Heikki Linnakangas | 2008-03-17 19:26:26 | Re: Rewriting Free Space Map |