WAL-files restore and nextval('PK') - Mailing list pgsql-sql

From Andreas Gaab
Subject WAL-files restore and nextval('PK')
Date
Msg-id 48DA836F3865C54B8FBF424A3B775AF6010D455863@Exchange-Server
Whole thread Raw
Responses Re: WAL-files restore and nextval('PK')
Re: WAL-files restore and nextval('PK')
List pgsql-sql

Dear all,

 

after an WAL-restore of our Postgres DB, we observe seemingly wrong values of our sequences.

 

We have two postgres server (8.4) with pgpool in replication mode.

 

Recently we tested our restore procedure and played our WAL-files into the second server after an old file-system backup was restored.

Accidently, we aborted the starting server and had to restart it and therefore started WAL-replay again.

 

Now we observe, that the newly restored server has higher values in his sequences as the other server.

 

Could it be that during restart of the WAL-file restore SELECT nextval(‘PK’) ; commands were executed again, whereas the data rows were already restored and thus leading to higher sequence numbers on the newly restored server?

 

Best regards for any comments!

 

Andreas

 

 

___________________________________________________________________________

 

SCANLAB AG

Dr. Andreas Simon Gaab

Entwicklung • R & D

 

Siemensstr. 2a • 82178 Puchheim • Germany

Tel. +49 (89) 800 746-513 • Fax +49 (89) 800 746-199

mailto:a.gaab@scanlab.dewww.scanlab.de

 

Amtsgericht München: HRB 124707 • USt-IdNr.: DE 129 456 351

Vorstand: Georg Hofner (Sprecher), Christian Huttenloher, Norbert Petschik

Aufsichtsrat (Vorsitz): Dr. Hans J. Langer

___________________________________________________________________________

 

pgsql-sql by date:

Previous
From: Kaveh Mousavi Zamani
Date:
Subject: Prevent Domain Compare
Next
From: Tom Lane
Date:
Subject: Re: WAL-files restore and nextval('PK')