Re: duplicate key value violates unique constraint

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Ashkar Dev <ashkardev(at)gmail(dot)com>
Cc: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: duplicate key value violates unique constraint
Date: 2020-03-07 19:55:02
Message-ID: CAKFQuwaVzH=1UMQr74uM_kLkZVDky+4ei8ufE6QFM9LHQHQ8rQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general

On Sat, Mar 7, 2020 at 12:35 PM Ashkar Dev <ashkardev(at)gmail(dot)com> wrote:

>
> Hi all,
>
> how to fix a problem, suppose there is a table with id and username
>

You should probably provide the definition though in this case it is
self-evident that you are using bigserial.

> So it doesn't start again from non-available id 1, so what is needed to do
> to make the new inserts go into non-available id numbers?
>

Alter sequence

https://www.postgresql.org/docs/12/sql-altersequence.html

> and if the id reaches the limit and maybe there is some ids that are not
> used.
>

This is highly unlikely.

Is the subject line supposed to relate to this in some way?

You should not worry about any of this in production; and frankly, worrying
about it in development is largely pointless as well.

There is no actual problem here to be fixed.

David J.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Ashkar Dev 2020-03-07 20:21:32 Re: duplicate key value violates unique constraint
Previous Message Dave Bolt 2020-03-07 19:54:20 RE: duplicate key value violates unique constraint

Browse pgsql-general by date

  From Date Subject
Next Message Ashkar Dev 2020-03-07 20:21:32 Re: duplicate key value violates unique constraint
Previous Message Dave Bolt 2020-03-07 19:54:20 RE: duplicate key value violates unique constraint