| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Alban Hertroys <alban(at)magproductions(dot)nl> |
| Cc: | John Tregea <john(at)debraneys(dot)com>, Scott Ribe <scott_ribe(at)killerbytes(dot)com>, Kenneth Downs <ken(at)secdat(dot)com>, Tim Allen <tim(at)proximity(dot)com(dot)au>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Return the primary key of a newly inserted row? |
| Date: | 2006-06-26 13:00:28 |
| Message-ID: | 20060626130028.GF24611@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jun 26, 2006 at 11:31:32AM +0200, Alban Hertroys wrote:
> [1] Unless you manage to make it wrap around after 2^32 (or 2^64?) calls
> of nextval. But that's quite unlikely.
Even then, only if have wrapping enabled. With wrapping disabled,
nextval() will simply fail rather than return a value already returned.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-06-26 13:23:13 | Re: unique attributes in profile management system |
| Previous Message | Martijn van Oosterhout | 2006-06-26 12:49:46 | Re: update impossible, constraint prevents it but it shouldn't |