RE: Status of new relation file naming - Mailing list pgsql-hackers

From Hiroshi Inoue
Subject RE: Status of new relation file naming
Date
Msg-id 000701c01ea9$85de0440$2801007e@tpf.co.jp
Whole thread Raw
In response to RE: Status of new relation file naming  ("Mikheev, Vadim" <vmikheev@SECTORBASE.COM>)
List pgsql-hackers
> -----Original Message-----
> From: Mikheev, Vadim [mailto:vmikheev@SECTORBASE.COM]
>
> > > Rename... Why would we need in rename with OID filenames?
> >
> > Andreas seems to refer to in place replacement of OID files e.g.
> > using your *relink*.
>
> Sorry, I've messed things for myself.
>
> Ok. In short, I vote for UNIQUE_ID (unrelated to pg_class.oid) file names.
> I think that it's better to implement this (but neither OID nor
> OID.VERSION)
> right now
> because of this is like what we'll have in new smgr -
> tablespace_id.relation_file_node.
> Pg_class' OID is kind of logical things, totaly unrelated to the issue
> how/where to
> store relation file.
>
> Please comment ASAP.
>

Philip Warner mentioned about the advantage of random number.
It's exactly what I've wanted to say.

>> it removes the temptation to write utilities that rely on
>> the internal representation of our data.

It is preferable that file naming rule is encapsulated so that we
can change it without notice.

Regards.

Hiroshi Inoue



pgsql-hackers by date:

Previous
From: "Mikheev, Vadim"
Date:
Subject: RE: strange behaviour (bug)
Next
From: The Hermit Hacker
Date:
Subject: RE: Status of new relation file naming