From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Rick Delaney <rick(at)consumercontact(dot)com> |
Cc: | Adriaan Joubert <a(dot)joubert(at)albourne(dot)com>, admin <admin(at)wtbwts(dot)com>, pgsql-general(at)postgreSQL(dot)org |
Subject: | Re: Oids vs Serial fields (was Re: [GENERAL] searching oid's) |
Date: | 2000-01-14 16:43:37 |
Message-ID: | 200001141643.LAA01175@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Adriaan Joubert wrote:
> >
> > Yes oids get dumped with the -o flag. That is why I said automatically. Fact
> > remains that you cannot manipulate oids. Should you ever want to copy a table into
> > an exisiting system you would have to do a new initdb to make sure that the oids
> > in your table are not in use. And if anything ever gets corrupted it is much
> > harder to recover and fix it, as you have no control over the oid values that the
> > system assigns. I would definitely recommend a separate serial value, and I
> > believe this is also what is recommended in the postgres docs.
>
> You make some good points, but where is this recommended in the docs? I'd like
> to see more of "serial vs oid" if there is something.
>
> Bruce's book doesn't recommend one over the other, though it does mention some
> oid limitations. It doesn't mention that the sequence for a serial value isn't
> dropped when its table is, btw.
Is there some issue in the comparison I missed?
That is a good point about the sequence not being dropped.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Jose Soares | 2000-01-14 17:14:27 | Re: [GENERAL] How to get number of the week from datetime? |
Previous Message | Patrick Welche | 2000-01-14 16:19:17 | Date format |