Re: all serial type was changed to 1

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Max Wang <mwang(at)1080agile(dot)com>
Cc: "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 06:09:44
Message-ID: CAH2-Wz=3K7H9oJKbAmdwdD48RGsQxs=YTtnA5hqTcvN7mgZzsA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Apr 30, 2017 at 10:51 PM, Max Wang <mwang(at)1080agile(dot)com> wrote:
> 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.

I've heard of this happening before. I never determined what the cause was.

--
Peter Geoghegan

VMware vCenter Server
https://www.vmware.com/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Philippe BEAUDOIN 2017-05-01 06:54:56 Column rename in an extension update script
Previous Message Max Wang 2017-05-01 05:51:22 all serial type was changed to 1