| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Geoffrey <esoteric(at)3times25(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org, pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: [NOVICE] OID Question |
| Date: | 2004-11-11 21:01:46 |
| Message-ID: | 20041111210146.GA32254@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-novice |
On Thu, Nov 11, 2004 at 15:34:14 -0500,
Geoffrey <esoteric(at)3times25(dot)net> wrote:
>
> "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?
No. The unique constraint may result in a transaction failing that
wouldn't otherwise fail and your application needs to be able to handle
this case.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dawid Kuroczko | 2004-11-11 21:03:48 | Re: comp.database.postgresql.* |
| Previous Message | Martijn van Oosterhout | 2004-11-11 20:42:57 | Re: [NOVICE] OID Question |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Geoffrey | 2004-11-11 21:14:32 | Re: version changes |
| Previous Message | Martijn van Oosterhout | 2004-11-11 20:42:57 | Re: [NOVICE] OID Question |