From: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | RE: Big 7.1 open items |
Date: | 2000-06-16 03:57:44 |
Message-ID: | 000501bfd747$067f0220$2801007e@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
>
> "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> writes:
> > Please add my opinion for naming rule.
>
> > relname/unique_id but need some work new
> pg_class column,
> > no relname change. for unique-id generation filename not relname
>
> Why is a unique ID better than --- or even different from ---
> using the relation's OID? It seems pointless to me...
>
For example,in the implementation of CLUSTER command,
we would need another new file for the target relation in
order to put sorted rows but don't we want to change the
OID ? It would be needed for table re-construction generally.
If I remember correectly,you once proposed OID+version
naming for the cases.
Regards.
Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 2000-06-16 04:01:05 | Re: postgresql.org ftp troubles? |
Previous Message | Tom Lane | 2000-06-16 03:43:41 | Re: Big 7.1 open items |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-06-16 04:57:00 | Re: coalesce view error |
Previous Message | Tom Lane | 2000-06-16 03:43:41 | Re: Big 7.1 open items |