Tom, If we have WITH NOOID, why not having a WITH OID32 and WITH OID64 (or something of a sort) as well (being OID32 the default and OID an alias to it)? The last would not be available on some systems (who will use a system that does not support long long as a database server anyway?) The wire protocol will always handle the (tableoid) long form, references will always store the long form... The OID32 would exist only to allow people to save space in tables that need OIDs but not the 64 bit version. -- Fernando Nasser Red Hat Canada Ltd. E-Mail: [EMAIL PROTECTED] 2323 Yonge Street, Suite #300 Toronto, Ontario M4P 2C9 ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
- Re: [HACKERS] OID wraparound: summary and proposal Tom Lane
- Re: [HACKERS] OID wraparound: summary and proposal Hiroshi Inoue
- Re: [HACKERS] OID wraparound: summary and proposal Nathan Myers
- Re: [HACKERS] OID wraparound: summary and proposal Hannu Krosing
- Re: [HACKERS] OID wraparound: summary and proposal Bruce Momjian
- Re: [HACKERS] OID wraparound: summary and proposal Hannu Krosing
- Re: [HACKERS] OID wraparound: summary and proposal Tatsuo Ishii
- Re: [HACKERS] OID wraparound: summary and proposal Tom Lane
- Re: [HACKERS] OID wraparound: summary and proposal Hannu Krosing
- Re: [HACKERS] OID wraparound: summary and proposal Fernando Nasser
- Re: [HACKERS] OID wraparound: summary and proposal Bruce Momjian
- Re: [HACKERS] OID wraparound: summary and proposal Tom Lane
- Re: [HACKERS] OID wraparound: summary and proposal Fernando Nasser
- Re: [HACKERS] OID wraparound: summary and proposal Tom Lane
- Re: [HACKERS] OID wraparound: summary and proposal Tatsuo Ishii