| From: | Doug Fields <dfields-pg-general(at)pexicom(dot)com> |
|---|---|
| To: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Altering existing table to be WITHOUT OIDs |
| Date: | 2002-05-24 19:04:05 |
| Message-ID: | 5.1.0.14.2.20020524150206.02c27d88@mail.pexicom.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>I don't know of a way. However, keep in mind that WITHOUT OIDS is not
>(currently) a storage optimization -- the OID field is still stored on disk.
>The WITHOUT OIDS option is primarily for people who might be in danger
>of OID-wraparound.
Thanks. Yes, I am aware that it is not a storage optimization; however, I
may be adding 25 million + records to some tables each day, and this will
quickly wrap any 31 or 32 bit number. I actually use OIDs on one table as a
pkey (really a way to attempt the enforcing of a UNIQUE constraint without
the overhead of a 4 or 5 column index) and don't want them wrapping.
Cheers,
Doug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Doug Fields | 2002-05-24 19:10:45 | Re: Efficiency question: VARCHAR with empty string |
| Previous Message | Darren Ferguson | 2002-05-24 19:03:06 | Re: Case Insensitive Data Type |