| From: | Bo Lorentsen <bl(at)netgroup(dot)dk> |
|---|---|
| To: | "pgsql-general postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: OID Usage |
| Date: | 2005-01-14 23:06:41 |
| Message-ID: | 41E85081.8030204@netgroup.dk |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Martijn van Oosterhout wrote:
>It means using OIDs as you described has very well known problems and
>they will break on you eventually. You can mitigate the damage by
>creating a UNIQUE index on the oid column but you'd better be sure your
>application can handle the side-effects.
>
>
Ok, Tom told me about the same :-( But why are oid's still in PG, that
are they good for ? Will there be a real unique row id, like there is in
Oracle, or will this be keept as an internal value only ?
>OIDs won't become obsolete, but they'll probably no longer be enabled
>by default at some stage.
>
>
Is this because some old application's using oid's in somewhat small
dataset ?
>Hope this helps,
>
>
It did thanks.
/BL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bo Lorentsen | 2005-01-14 23:10:28 | Re: OID Usage |
| Previous Message | Bo Lorentsen | 2005-01-14 23:01:18 | Re: OID Usage |