Re: duplicate key value violates unique constraint "chinese_price_infos_pkey"

On 06/05/2019 12:05, Arup Rakshit wrote:
> Every time I try to insert I get the error:
>
> docking_dev=# INSERT INTO "chinese_price_infos" ("item_code",
> "price_cents", "unit", "description", "company_id", "created_at",
> "updated_at") VALUES ('01GS10001', 6000, 'Lift', 'Shore Crane
> Rental', '9ae3f8b8-8f3f-491c-918a-efd8f5100a5e', '2019-05-06
> 10:49:03.894725', '2019-05-06 10:49:03.894725'); ERROR: duplicate
> key value violates unique constraint "chinese_price_infos_pkey"
> DETAIL: Key (id)=(71165) already exists. docking_dev=# INSERT INTO
> "chinese_price_infos" ("item_code", "price_cents", "unit",
> "description", "company_id", "created_at", "updated_at") VALUES
> ('01GS10001', 6000, 'Lift', 'Shore Crane Rental',
> '9ae3f8b8-8f3f-491c-918a-efd8f5100a5e', '2019-05-06 10:49:03.894725',
> '2019-05-06 10:49:03.894725'); ERROR: duplicate key value violates
> unique constraint "chinese_price_infos_pkey" DETAIL: Key
> (id)=(71166) already exists.
>
> Then I found:
>
> docking_dev=# SELECT MAX(id) FROM chinese_price_infos; max --------
> 128520 (1 row)
>
> docking_dev=# SELECT nextval('chinese_price_infos_id_seq'); nextval
> --------- 71164 (1 row)
>
> Not sure how it is out of sync. How can I fix this permanently. I ran
> vacuum analyze verbose; still same error.

You can fix it by using setval() to set the sequence manually to
something higher than the highest current id value in the table.
However, it sounds as if something in the application code may be
causing problems.... For example, is something generating id values
without reference to the sequence?

Ray.

--
Raymond O'Donnell // Galway // Ireland
ray(at)rodonnell(dot)ie