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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Marc Schablewski <ms(at)clickware(dot)de>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4565: nextval not updated during wal replication, leading to pk violations
Date: 2008-12-09 13:10:15
Message-ID: 12890.1228828215@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Marc Schablewski <ms(at)clickware(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Nat! 2008-12-09 14:07:03 BUG #4574: LIKE fails on non-varying character with no wildcards
Previous Message Dave Page 2008-12-09 13:06:25 Re: BUG #4573: download problem