From: Peter Eisentraut <peter_e@gmx.net>
To: Michal Dobaczewski <mdobaczewski@cc.com.pl>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: libpq: usage of PQoidValue to obtain serial primary key after insert
Date: Thu, 22 Jul 2004 19:54:15 +0200
Message-ID: <200407221954.15525.peter_e@gmx.net> (raw)
In-Reply-To: <40FFC654.9000903@cc.com.pl>
References: <40FFA197.9080106@cc.com.pl>
<200407221444.56693.peter_e@gmx.net>
<40FFC654.9000903@cc.com.pl>
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/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: peter_e@gmx.net, mdobaczewski@cc.com.pl
Subject: Re: libpq: usage of PQoidValue to obtain serial primary key after insert
In-Reply-To: <200407221954.15525.peter_e@gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox