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 8825.1228951917@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>)
List pgsql-bugs
Marc Schablewski <ms@clickware.de> writes:
> Now everything seems to work fine, but we are still testing. At least
> what we see in the logs is more reasonable. Now the .backup file is
> requested first, then the WALs. There is one strange thing left, though.
> The server first requests the second WAL, then the first one, then the
> second again and then it processes them in order (second, third, fourth,
> ...). Is this normal?

It doesn't surprise me if something like that happens during PITR
startup.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bug in plpgsql, when using NEW with composite field value.
Next
From: "Scott Carey"
Date:
Subject: BUG #4575: All page cache in shared_buffers pinned (duplicated by OS, always)