pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
failed insert into serial-type row
5+ messages / 4 participants
[nested] [flat]

* failed insert into serial-type row
@ 2005-06-13 19:58 Hortschitz, Stefan <Stefan.Hortschitz@lfrz.at>
  2005-06-18 14:05 ` Re: failed insert into serial-type row Greg Sabino Mullane <greg@turnstep.com>
  2005-06-18 14:06 ` Re: failed insert into serial-type row Bruno Wolff III <bruno@wolff.to>
  0 siblings, 2 replies; 5+ messages in thread

From: Hortschitz, Stefan @ 2005-06-13 19:58 UTC (permalink / raw)
  To: pgsql-admin

hi, 

i'm working with an postgresql-installation on Solaris ("PostgreSQL
7.4.7 on sparc-sun-solaris2.9, compiled by GCC 2.95.3") and I have the
following problem: 
 
I'm using tables like this:
--------------------------------
CREATE TABLE session.preferences
(
  id serial NOT NULL,
  name varchar(50),
  value varchar(255),
  CONSTRAINT session_preferences_pkey PRIMARY KEY (id)
) 
WITHOUT OIDS;
ALTER TABLE session.preferences OWNER TO web;
--------------------------------

and sometimes if i'm adding new rows to the table with statements like
this:
      insert into (name,value) ('xy','xy');
the database only returns an 'duplicate key on primary key', which
should be prevented by the serial-datatype, or? how could it be, that
two rows become the same id??
if i execute the insert-statement again it works.

the created serial-sequence looks like this: 
--------------------------------
CREATE SEQUENCE session.preferences_id_seq
  INCREMENT 1
  MINVALUE 1
  MAXVALUE 9223372036854775807
  START 2487
  CACHE 1;
ALTER TABLE session.preferences_id_seq OWNER TO web;
--------------------------------

what can I do against the duplicate-key problem? is it a configuration,
sql or operating-system specific problem?

with kind regards 
stefan



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: failed insert into serial-type row
  2005-06-13 19:58 failed insert into serial-type row Hortschitz, Stefan <Stefan.Hortschitz@lfrz.at>
@ 2005-06-18 14:05 ` Greg Sabino Mullane <greg@turnstep.com>
  1 sibling, 0 replies; 5+ messages in thread

From: Greg Sabino Mullane @ 2005-06-18 14:05 UTC (permalink / raw)
  To: pgsql-admin; +Cc: Stefan.Hortschitz@lfrz.at


-----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@turnstep.com
PGP Key: 0x14964AC8 200506180957
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iD8DBQFCtCoLvJuQZxSWSsgRAkiVAKDG6eVWdCdqzbnQnqIOHyoZ/ijzOACfcgh+
9P9fUQbyJUXebzHvOf4F3Z8=
=QKrK
-----END PGP SIGNATURE-----






^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: failed insert into serial-type row
  2005-06-13 19:58 failed insert into serial-type row Hortschitz, Stefan <Stefan.Hortschitz@lfrz.at>
@ 2005-06-18 14:06 ` Bruno Wolff III <bruno@wolff.to>
  1 sibling, 0 replies; 5+ messages in thread

From: Bruno Wolff III @ 2005-06-18 14:06 UTC (permalink / raw)
  To: Hortschitz, Stefan <Stefan.Hortschitz@lfrz.at>; +Cc: pgsql-admin

On Mon, Jun 13, 2005 at 21:58:37 +0200,
  "Hortschitz, Stefan" <Stefan.Hortschitz@lfrz.at> wrote:
>  
> CREATE TABLE session.preferences
> (
>   id serial NOT NULL,
>   name varchar(50),
>   value varchar(255),
>   CONSTRAINT session_preferences_pkey PRIMARY KEY (id)
> ) 
> WITHOUT OIDS;
> ALTER TABLE session.preferences OWNER TO web;
> --------------------------------
> 
> and sometimes if i'm adding new rows to the table with statements like
> this:
>       insert into (name,value) ('xy','xy');
> the database only returns an 'duplicate key on primary key', which
> should be prevented by the serial-datatype, or? how could it be, that
> two rows become the same id??
> if i execute the insert-statement again it works.
> 
> the created serial-sequence looks like this: 
> --------------------------------
> CREATE SEQUENCE session.preferences_id_seq
>   INCREMENT 1
>   MINVALUE 1
>   MAXVALUE 9223372036854775807
>   START 2487
>   CACHE 1;
> ALTER TABLE session.preferences_id_seq OWNER TO web;
> --------------------------------
> 
> what can I do against the duplicate-key problem? is it a configuration,
> sql or operating-system specific problem?

Most likely you recreated the table and reloaded it at some point without
restoring the sequence value.

What you want to do now is set the sequence to the highest value of id
in the table. Something like:
SELECT setval('preferences_id_seq',(SELECT max(id) FROM session.preferences);




^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* failed insert into serial-type row
@ 2005-06-14 05:28 Hortschitz, Stefan <Stefan.Hortschitz@lfrz.at>
  2005-06-18 13:52 ` Re: failed insert into serial-type row Michael Fuhr <mike@fuhr.org>
  0 siblings, 1 reply; 5+ messages in thread

From: Hortschitz, Stefan @ 2005-06-14 05:28 UTC (permalink / raw)
  To: pgsql-admin

hi, 

 

i'm working with an postgresql-installation on Solaris ("PostgreSQL
7.4.7 on sparc-sun-solaris2.9, compiled by GCC 2.95.3") and I have the
following problem: 

 

I'm using tables like this:

--------------------------------

CREATE TABLE session.preferences

(

  id serial NOT NULL,

  name varchar(50),

  value varchar(255),

  CONSTRAINT session_preferences_pkey PRIMARY KEY (id)

) 

WITHOUT OIDS;

ALTER TABLE session.preferences OWNER TO web;

--------------------------------

 

and sometimes if i'm adding new rows to the table with statements like
this:

      insert into (name,value) ('xy','xy');

the database only returns an 'duplicate key on primary key', which
should be prevented by the serial-datatype, or? how could it be, that
two rows become the same id??

if i execute the insert-statement again it works.

 

the created serial-sequence looks like this: 

--------------------------------

CREATE SEQUENCE session.preferences_id_seq

  INCREMENT 1

  MINVALUE 1

  MAXVALUE 9223372036854775807

  START 2487

  CACHE 1;

ALTER TABLE session.preferences_id_seq OWNER TO web;

--------------------------------

 

what can I do against the duplicate-key problem? is it a configuration,
sql or operating-system specific problem?

 

with kind regards 

stefan

 

 

^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: failed insert into serial-type row
  2005-06-14 05:28 failed insert into serial-type row Hortschitz, Stefan <Stefan.Hortschitz@lfrz.at>
@ 2005-06-18 13:52 ` Michael Fuhr <mike@fuhr.org>
  0 siblings, 0 replies; 5+ messages in thread

From: Michael Fuhr @ 2005-06-18 13:52 UTC (permalink / raw)
  To: Hortschitz, Stefan <Stefan.Hortschitz@lfrz.at>; +Cc: pgsql-admin

On Tue, Jun 14, 2005 at 07:28:22AM +0200, Hortschitz, Stefan wrote:
> 
> sometimes if i'm adding new rows to the table with statements like
> this:
> 
>       insert into (name,value) ('xy','xy');
> 
> the database only returns an 'duplicate key on primary key', which
> should be prevented by the serial-datatype, or? how could it be, that
> two rows become the same id??

One possibility is that the table contains IDs that are higher than
the sequence value, so you occasionally get duplicates when you use
the sequence.  What are the results of the following queries?

SELECT max(id) FROM session.preferences;
SELECT * FROM session.preferences_id_seq;

If max(id) is higher than the sequence's last_value, then you can
adjust the sequence with setval() or ALTER SEQUENCE.  Then you
should to figure out how that happened so you can prevent it from
happening again.

-- 
Michael Fuhr
http://www.fuhr.org/~mfuhr/



^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2005-06-18 14:06 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-06-13 19:58 failed insert into serial-type row Hortschitz, Stefan <Stefan.Hortschitz@lfrz.at>
2005-06-18 14:05 ` Greg Sabino Mullane <greg@turnstep.com>
2005-06-18 14:06 ` Bruno Wolff III <bruno@wolff.to>
2005-06-14 05:28 failed insert into serial-type row Hortschitz, Stefan <Stefan.Hortschitz@lfrz.at>
2005-06-18 13:52 ` Michael Fuhr <mike@fuhr.org>

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