From: | Max Wang <mwang(at)1080agile(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: all serial type was changed to 1 |
Date: | 2017-05-01 23:08:30 |
Message-ID: | ME1PR01MB13944BA9152442186ECBD58BA8140@ME1PR01MB1394.ausprd01.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Adrian,
Only sequences (id) reset to 1.
Regards,
Max
-----Original Message-----
From: Adrian Klaver [mailto:adrian(dot)klaver(at)aklaver(dot)com]
Sent: Monday, 1 May 2017 11:30 PM
To: Max Wang <mwang(at)1080agile(dot)com>; pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] all serial type was changed to 1
On 04/30/2017 10:51 PM, Max Wang wrote:
> Hi All,
>
>
>
> We have a PostgreSQL database. There are 26 tables and we use serial
> type as primary key. We had a insert error as "duplicate key value
> violates unique constraint, DETAIL: Key (id)=(1) already exists." one
> weeks ago. I checked and found all tables' id were reset to 1.
So to be clear:
Every row in each of the 26 tables has an id of 1?
or
Do you mean the sequences where reset to 1?
>
>
>
> I checked database log and did not find any useful information. I am
> not sure why this happen. The only script which connect to this
> database is a Python script and only do normal insert/update/delete actions.
>
>
>
> Please give me some suggestions if you happen to know something about
> this issue. I appreciate any feedback you might have.
>
>
>
> I am very new to PostgreSQL and this mail list. Please let me know if
> I did not something wrong.
>
>
>
> Thank you.
>
>
>
> Regards,
>
> Max
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Max Wang | 2017-05-01 23:11:51 | Re: all serial type was changed to 1 |
Previous Message | Max Wang | 2017-05-01 23:07:45 | Re: all serial type was changed to 1 |