From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Michal Dobaczewski <mdobaczewski(at)cc(dot)com(dot)pl> |
Cc: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: libpq: usage of PQoidValue to obtain serial primary key after insert |
Date: | 2004-07-22 17:54:15 |
Message-ID: | 200407221954.15525.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Michal Dobaczewski wrote:
> I wonder: how will postgres behave if it happens to generate a
> repetitive oid for a table with such constraint?
You get a constraint violation error.
> I understand it will
> work it out somehow internally and get a different oid,
No.
> but I would
> like to be sure. It doesn't create a risk of inserts failing at
> random, does it?
Yes, it would (for certain definitions of "random").
> I also understand this theoretically limits the number of rows in a
> table to 2^32 whereas without such constraint there is no set limit -
> is that true? It's not a problem, we don't have such big tables so
> far but it would be interesting to know.
If you're concerned about that, you better go back to sequences and use
bigserial columns.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
From | Date | Subject | |
---|---|---|---|
Next Message | Brett Schwarz | 2004-07-29 23:00:31 | Re: Pgaccess questions |
Previous Message | Peter Eisentraut | 2004-07-22 17:51:39 | Re: NULLs in ecpg |