From: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Cc: | Stefan(dot)Hortschitz(at)lfrz(dot)at |
Subject: | Re: failed insert into serial-type row |
Date: | 2005-06-18 14:05:32 |
Message-ID: | e5a11b1c3eaf4ea91b2636e6764690e9@biglumber.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> and sometimes if i'm adding new rows to the table with statements like
> this:
> insert into (name,value) ('xy','xy');
Show us the actual SQL, not something "like" it. The above is not valid.
> CREATE SEQUENCE session.preferences_id_seq
> START 2487
You haven't shown us how this sequence is attached to the table. Presumably
with:
ALTER TABLE preferences ALTER id SET DEFAULT nextval('preferences_id_seq');
That START qualifier is a red flag. If the sequence was not created when the table
was, one explanation is that there are existing values in the table that are higher
than the current sequence. Running
SELECT max(id) FROM preferences
and
SELECT * FROM preferences_id_seq;
should show that. The other possibility is that someone is inserting into the table
and specifying a value for the id field manually.
- --
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 200506180957
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iD8DBQFCtCoLvJuQZxSWSsgRAkiVAKDG6eVWdCdqzbnQnqIOHyoZ/ijzOACfcgh+
9P9fUQbyJUXebzHvOf4F3Z8=
=QKrK
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2005-06-18 14:06:10 | Re: failed insert into serial-type row |
Previous Message | Greg Sabino Mullane | 2005-06-18 13:56:26 | Re: getting a sequence to update properly |