| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Hannu Krosing <hannu(at)tm(dot)ee> |
| Cc: | mlw <markw(at)mohawksoft(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: OID wraparound: summary and proposal |
| Date: | 2001-08-03 00:40:35 |
| Message-ID: | 14999.996799235@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hannu Krosing <hannu(at)tm(dot)ee> writes:
> That would probably be a problem with 4-byte OIDs, there is an ample
> supply of 8-byte ones
Sure, but I think we are still a few years away from being able to
assume that every platform of interest can support 8-byte OIDs (and
furthermore, won't see a significant performance degradation --- keep
in mind that widening Datum to 8 bytes is a change that affects all
datatypes not just Oid). There's also the Oids-are-in-the-wire-protocol
problem. In short, that's a long-term solution not a near-term one.
> BTW, don't indexes, triggers or saved plans use OIDs from pg_attribute ?
Nope. pg_description is the only offender.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2001-08-03 01:07:40 | Re: AW: OID wraparound: summary and proposal |
| Previous Message | Tom Lane | 2001-08-03 00:11:37 | Rules for updatable views (was Re: [PATCHES] Revised Patch to allow multiple table locks in "Unison") |