Bruce Momjian <[EMAIL PROTECTED]> writes: > This is a very interesting idea. Have two oid counters, one for system > tables and another for user tables. It isolates problems with oid > wraparound caused by large user tables. Well, it'd keep user-space wraparound from affecting the system tables, but given that the system tables have adequate defenses already (ie, unique indexes) I'm not sure that there's any point. It'd not improve the picture for user-table OID uniqueness by any measurable degree. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
- 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