From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
---|---|
To: | Hannu Krosing <hannu(at)tm(dot)ee>, "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
Cc: | "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "'hackers(at)postgresql(dot)org'" <hackers(at)postgresql(dot)org> |
Subject: | Re: Status of new relation file naming |
Date: | 2000-09-13 09:02:22 |
Message-ID: | 3.0.5.32.20000913190222.028fb7b0@mail.rhyme.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At 09:44 13/09/00 +0300, Hannu Krosing wrote:
>"Mikheev, Vadim" wrote:
>>
>> > My idea was to append a version number or oid on to the end
>> > of the file name, and use that somehow.
>>
>> You'll lose all you would buy as soon as we'll begin to store many
>> relations in single file...
>
>Perhaps we could then use the name of DATASPACE = filename ?
>
I don't want to (re)^n ignite the the debate, but file naming has been
discussed many times before and my recollection of the result of the last
debate was that the names should either be random or OID based. It seems
that adding a different meaning to filenames at this stage would be a bad
idea, and doom us to repeat the file naming debate again in a year or two.
My vote is for a random number, and then someone can write the tools to
display the file info. I'll even volunteer to work on them...
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2000-09-13 10:41:04 | Re: PL/pgSQL does not accept none ASCII identifiers |
Previous Message | Andreas Degert | 2000-09-13 08:59:30 | alter table rename to .. |