| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Michael Glaesemann" <grzm(at)seespotcode(dot)net> |
| Cc: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net>, Postgres-General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Using oid as pkey |
| Date: | 2007-08-20 22:30:48 |
| Message-ID: | dcc563d10708201530q7e6c3a8dtfee711cc1c142f0f@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 8/20/07, Michael Glaesemann <grzm(at)seespotcode(dot)net> wrote:
>
> On Aug 20, 2007, at 16:58 , Ed L. wrote:
>
> > What are the concerns with using oid as the column for a primary
> > key declaration for use in trigger-based replication?
>
> Just don't. oids are intended to be used by the database server
> itself rather than as part of the user-defined data. If you're
> looking for a auto-generated integer to use as a primary key, use
> SERIAL. You'd have to specify your table WITH OIDS anyway as they're
> no longer used by default for table rows, so there's really nothing
> to be gained by using oids.
And they wrap around, so there's a chance of collision with oids.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | D. Dante Lorenso | 2007-08-20 22:51:09 | Re: Using oid as pkey |
| Previous Message | Michael Glaesemann | 2007-08-20 22:10:25 | Re: Using oid as pkey |