Autoincrement not updating

Bug report

Describe the bug

This seems to have only started occurring in the last couple of days.

When I seed a table during a migration (below), upon insertion the autoincrement id of the table does not seem to trigger.

The first two INSERT calls to this table from the frontend client return a duplicate key error:

{
code: "23505",
details: null,
hint: null,
message: "duplicate key value violates unique constraint \"api_keys_pkey\""
}

However, upon the third insert attempt - the row is created successfully.

-- CreateTable
CREATE TABLE api_keys
(
  id          bigint GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY,
  team_id     bigint REFERENCES teams ( id ) ON DELETE CASCADE ON UPDATE CASCADE NOT NULL,
  creator_id  uuid REFERENCES accounts ( id ) ON DELETE CASCADE ON UPDATE CASCADE DEFAULT auth.uid( ),
  token       uuid NOT NULL UNIQUE DEFAULT uuid_generate_v4( ),
  created_at  timestamp WITH TIME ZONE DEFAULT timezone( 'utc'::text, NOW( ) ) NOT NULL,
  updated_at  timestamp WITH TIME ZONE DEFAULT timezone( 'utc'::text, NOW( ) ) NOT NULL,
  disabled_at timestamp WITH TIME ZONE
);

-- InsertInto
INSERT INTO api_keys ( id, team_id, creator_id )
VALUES ( 1, 1, '2bc32eba-533d-42fc-9402-b12b9af79c75' );
INSERT INTO api_keys ( id, team_id, creator_id )
VALUES ( 2, 2, '8cb12f23-533d-4032-ab1d-946d530eda69' );

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Define a table with an autoincrementing id column, followed by two INSERT queries to the new table.
2. Execute SQL via the Supabase GUI.
3. Attempt to insert a new row either from the frontend client or direct SQL connection.
4. See duplicate key value violation first two attempts and success on the third attempt.

Expected behavior

Autoincrement should not care how the row is inserted (via Supabase GUI SQL script or remote access).

Screenshots

System information

• OS: N/A
• Browser (if applies): Edge
• Version of supabase-js: "@supabase/supabase-js": "^1.13.1"
• Version of Node.js: 14

[amirhosein5858]

ALTER SEQUENCE <your_sequence> RESTART WITH 1500

thanks to you i try SELECT PG_GET_SERIAL_SEQUENCE('table', 'id'); to find right seq and then run ALTER SEQUENCE <your_sequence> RESTART WITH 453 as you say and it worked thank you very much

[soedirgo]

Hey @prescience-data, identity columns like id here are sequences, so if you insert a value manually it’ll clash with the sequence (more info here). Unfortunately, AFAIK there is no way for it to detect already existing values (unlike, say, MySQL’s auto_increment).

You might consider using DEFAULT in place of 1 and 2 above, or alternatively you can sync them after seeding with:

SELECT setval('api_keys_id_seq', COALESCE((SELECT MAX(id)+1 FROM api_keys), 1), false);

This updates the id sequence’s next value to 3, so following inserts should work normally.