From: | Geoffrey <esoteric(at)3times25(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org, pgsql-novice(at)postgresql(dot)org |
Subject: | Re: [NOVICE] OID Question |
Date: | 2004-11-11 20:34:14 |
Message-ID: | 4193CCC6.3080505@3times25.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-novice |
Bruno Wolff III wrote:
> On Thu, Nov 11, 2004 at 10:04:30 -0500, Terry Lee Tucker
> <terry(at)esc1(dot)com> wrote:
>
>> Greetings,
>>
>> Here is a simple question:
>>
>> Is it ok to put a unique index on the oid for my tables? We are in
>> the process
>
>
> Yes, but you may occasionally have insert failures if the oid wraps
> around and you try to reuse one on an insert.
So this prompts a question regarding the documentation. I'm assuming
that I can address the wrap-around issue based on the following found
under "Notes" section of the "Create Table" document:
"Whenever an application makes use of OIDs to identify specific rows of
a table, it is recommended to create a unique constraint on the oid
column of that table, to ensure that OIDs in the table will indeed
uniquely identify rows even after counter wraparound."
Am I reading this correctly? If I place a unique constraint on the oid
column, I will not have to worry about oid wrap around?
--
Until later, Geoffrey
From | Date | Subject | |
---|---|---|---|
Next Message | jao | 2004-11-11 20:42:54 | Re: When to switch to Postgres 8.0? |
Previous Message | Andrew Rawnsley | 2004-11-11 20:26:21 | Re: comp.database.postgresql.* |
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2004-11-11 20:42:57 | Re: [NOVICE] OID Question |
Previous Message | Kevin B. | 2004-11-11 19:47:05 | version changes |