| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
| Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: OID wraparound: summary and proposal |
| Date: | 2001-08-07 15:28:43 |
| Message-ID: | 200108071528.f77FShH14433@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > Based on the discussion so far, here is an attempt to flesh out the
> > details of what to do with OIDs for 7.2:
> >
> > 1. Add an optional clause "WITH OIDS" or "WITHOUT OIDS" to CREATE TABLE.
> > The default behavior will be WITH OIDS.
>
> What about having an additional Oid generator which solely serves for
> supplying user tables' per row Oids? It seems relatively easy to
> implement, comparing with 64-bit Oids or Oid-less tables. I assume
> that the Oid wraparound problem is not so serious with user tables.
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.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-08-07 15:36:41 | Re: OID wraparound: summary and proposal |
| Previous Message | Tom Lane | 2001-08-07 15:22:23 | Re: Proposal: OID wraparound: summary and proposal |