| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu> |
| Subject: | Re: Big 7.1 open items |
| Date: | 2000-06-19 04:25:52 |
| Message-ID: | 9514.961388752@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> I also suggested creating an extent directory to hold extents, like
> extent/2 and extent/3. This will allow administration for smaller sites
> to be simpler.
I don't see the value in creating an extra level of directory --- seems
that just adds one more Unix directory-lookup cycle to each file open,
without any apparent return. What's wrong with extent directory names
like extent2, extent3, etc?
Obviously the extent dirnames must be chosen so they can't conflict
with table filenames, but that's easily done. For example, if table
files are named like 'OID_xxx' then 'extentN' will never conflict.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-06-19 04:28:14 | Re: Big 7.1 open items |
| Previous Message | Don Baccus | 2000-06-19 04:07:48 | Re: Big 7.1 open items |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-06-19 04:28:14 | Re: Big 7.1 open items |
| Previous Message | Don Baccus | 2000-06-19 04:07:48 | Re: Big 7.1 open items |