Re: BUG #4565: nextval not updated during wal replication, leading to pk violations

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