Re: Streaming replication: sequences on slave seemingly ahead of sequences on master - Mailing list pgsql-general

From Merlin Moncure
Subject Re: Streaming replication: sequences on slave seemingly ahead of sequences on master
Date
Msg-id CAHyXU0wjc3A2DUbtOcBXW-VgRjoi_yVi-GGyJ=jojmXQvF5iDw@mail.gmail.com
Whole thread Raw
In response to Streaming replication: sequences on slave seemingly ahead of sequences on master  (Vincent de Phily <vincent.dephily@mobile-devices.fr>)
Responses Re: Streaming replication: sequences on slave seemingly ahead of sequences on master
List pgsql-general
On Fri, May 4, 2012 at 8:55 AM, Vincent de Phily
<vincent.dephily@mobile-devices.fr> wrote:
> Hi list,
>
> we have two 9.1.2 servers on debian squeeze, and are setting up a simple
> streaming replication between the two.
>
> * wal_keep_segments is set high on the master
> * the slave's recovery.conf contains just standbay_mode=on and
>  primary_conninfo=foo
> * we use a simple start_backup/rsync/stop_backup to create the base copy
>  before starting the slave.
>
>
> It all seems to be working fine, except that when checking the data (selecting
> latest primary key and sequence value for all tables) on master and slave,
> some sequence ids are higher on the slave than on the master. I could
> understand if they were lower, but this is weird.
>
> * The slave's sequences can be anywhere between 1 and 50 ids ahead.

how did you determine that exactly?  how do you know the transactions
are committing in sequence order?

merlin

pgsql-general by date:

Previous
From: Vincent de Phily
Date:
Subject: Streaming replication: sequences on slave seemingly ahead of sequences on master
Next
From: Vincent de Phily
Date:
Subject: Re: Streaming replication: sequences on slave seemingly ahead of sequences on master