Re: BUG #4565: nextval not updated during wal replication, leading to pk violations - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #4565: nextval not updated during wal replication, leading to pk violations
Date
Msg-id 12890.1228828215@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #4565: nextval not updated during wal replication, leading to pk violations  (Marc Schablewski <ms@clickware.de>)
Responses Re: BUG #4565: nextval not updated during wal replication, leading to pk violations
List pgsql-bugs
Marc Schablewski <ms@clickware.de> writes:
> cache_value is set to one for all sequences. As far as I can tell, they
> were all created by a plain CREATE SEQUENCE seq_name and no other
> settings changed. And as we found out later this "loss of information"
> hit some indexes as well.

> We took a fresh backup yesterday and again we saw that only the last WAL
> generated during the backup run was restored on our backup system. I'm
> sure that this is the real problem.

This is beginning to sound like an error in your backup/restore
procedures.  Please describe exactly what you're doing.

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Dave Page"
Date:
Subject: Re: BUG #4573: download problem
Next
From: "Nat!"
Date:
Subject: BUG #4574: LIKE fails on non-varying character with no wildcards