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

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