On 05/01/2017 05:04 PM, Max Wang wrote:
Hi Adrian,
Thank you. The strange things is we only use Python do insert/update/delete
and do not run other SQL command.
The evidence says otherwise, which leads to:
So nothing ever pulls data out of the database with SELECTS?
There is no monitoring
pgsql-general@postgresql.org
Subject: Re: [GENERAL] all serial type was changed to 1
On 05/01/2017 04:29 PM, Max Wang wrote:
> Hi Adrian,
>
> I checked and found
>
> is_cycled | f
Hmm.
A possible cause:
test=# insert into serial_test (fld_1) values ('test'); INSE
t; Can you do that on the serial column from one the affected tables and post
> the results here?
>
>
>
>
> Thanks.
>
> Regards,
> Max
>
> -Original Message-
> From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
> Sent: Tuesday, 2 May 2017 9:31 A
On 05/01/2017 04:55 PM, Max Wang wrote:
Hi Melvin,
I already reset id to correct value after this happen. This is a
production database. We could not stop and wait for trouble shooting. I
manually reset sequence of id to correct value.
I would grep for setval in any of the code you have
c: Max Wang <mw...@1080agile.com>; Amitabh Kant <amitabhk...@gmail.com>;
pgsql-general@postgresql.org
Subject: Re: [GENERAL] all serial type was changed to 1
On Mon, May 1, 2017 at 7:45 PM, Adrian Klaver
<adrian.kla...@aklaver.com<mailto:adrian.kla...@aklaver.com>> wrot
ct: Re: [GENERAL] all serial type was changed to 1
On 05/01/2017 04:08 PM, Max Wang wrote:
Hi Adrian,
Only sequences (id) reset to 1.
Then per Amitabh Kant's suggestion take a look at the cycle setting for the
sequences.
For sequence named ts_stamp_test_id_seq:
test=# select * from ts_s
l Message-----
>> From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
>> Sent: Tuesday, 2 May 2017 9:31 AM
>> To: Max Wang <mw...@1080agile.com>; Amitabh Kant <amitabhk...@gmail.com>
>> Cc: pgsql-general@postgresql.org
>> Subject: Re: [GENERAL] all serial
AM
To: Max Wang <mw...@1080agile.com>; Amitabh Kant <amitabhk...@gmail.com>
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] all serial type was changed to 1
On 05/01/2017 04:11 PM, Max Wang wrote:
Hi Amitabh,
Thank you for suggestion. We did not reach the limit of serial type
...@aklaver.com]
Sent: Tuesday, 2 May 2017 9:31 AM
To: Max Wang <mw...@1080agile.com>; Amitabh Kant <amitabhk...@gmail.com>
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] all serial type was changed to 1
On 05/01/2017 04:11 PM, Max Wang wrote:
> Hi Amitabh,
>
>
>
> Thank
On Mon, May 1, 2017 at 7:31 PM, Adrian Klaver
wrote:
> On 05/01/2017 04:11 PM, Max Wang wrote:
>
>> Hi Amitabh,
>>
>>
>>
>> Thank you for suggestion. We did not reach the limit of serial type.
>> Some tables only have hundreds of rows.
>>
>
> It would helpful if you
On 05/01/2017 04:11 PM, Max Wang wrote:
Hi Amitabh,
Thank you for suggestion. We did not reach the limit of serial type.
Some tables only have hundreds of rows.
It would helpful if you ran the query I showed in my previous post on
one the sequences just so we can see.
From subsequent
Hi Adrian,
I checked and found
is_cycled | f
Regards,
Max
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
Sent: Tuesday, 2 May 2017 9:16 AM
To: Max Wang <mw...@1080agile.com>; pgsql-general@postgresql.org
Subject: Re: [GENERAL] all seria
laver.com>;
pgsql-general@postgresql.org
*Subject:* Re: [GENERAL] all serial type was changed to 1
On Mon, May 1, 2017 at 7:08 PM, Max Wang <mw...@1080agile.com
<mailto:mw...@1080agile.com>> wrote:
Hi Adrian,
Only sequences (id) reset to 1.
Regards,
Max
o:adrian.kla...@aklaver.com>]
Sent: Monday, 1 May 2017 11:30 PM
To: Max Wang <mw...@1080agile.com<mailto:mw...@1080agile.com>>;
pgsql-general@postgresql.org<mailto:pgsql-general@postgresql.org>
Subject: Re: [GENERAL] all serial type was changed to 1
On 04/30/2017 10:51 PM, Max Wa
On 05/01/2017 04:08 PM, Max Wang wrote:
Hi Adrian,
Only sequences (id) reset to 1.
Then per Amitabh Kant's suggestion take a look at the cycle setting for
the sequences.
For sequence named ts_stamp_test_id_seq:
test=# select * from ts_stamp_test_id_seq ;
-[ RECORD 1
> To: Max Wang <mw...@1080agile.com>; pgsql-general@postgresql.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
ubject: Re: [GENERAL] all serial type was changed to 1
On Mon, May 1, 2017 at 11:21 AM, Max Wang
<mw...@1080agile.com<mailto:mw...@1080agile.com>> 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 “d
Hi Adrian,
Only sequences (id) reset to 1.
Regards,
Max
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
Sent: Monday, 1 May 2017 11:30 PM
To: Max Wang <mw...@1080agile.com>; pgsql-general@postgresql.org
Subject: Re: [GENERAL] all serial type was change
pgsql-general@postgresql.org
Subject: Re: [GENERAL] all serial type was changed to 1
On 1 May 2017 at 17:51, Max Wang <mw...@1080agile.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
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
On 1 May 2017 at 17:51, Max Wang 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
>
On Mon, May 1, 2017 at 11:21 AM, 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.”
On Sun, Apr 30, 2017 at 10:51 PM, Max Wang 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
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.
I checked
24 matches
Mail list logo