From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Vincent de Phily <vincent(dot)dephily(at)mobile-devices(dot)fr> |
Cc: | pgsql-general(at)postgresql(dot)org, benjamin(dot)vialle(at)mobile-devices(dot)fr |
Subject: | Re: Streaming replication: sequences on slave seemingly ahead of sequences on master |
Date: | 2012-05-04 14:47:16 |
Message-ID: | CAHyXU0wjc3A2DUbtOcBXW-VgRjoi_yVi-GGyJ=jojmXQvF5iDw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, May 4, 2012 at 8:55 AM, Vincent de Phily
<vincent(dot)dephily(at)mobile-devices(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Ingmar Brouns | 2012-05-04 16:10:24 | set returning functions and resultset order |
Previous Message | Vincent de Phily | 2012-05-04 13:55:48 | Streaming replication: sequences on slave seemingly ahead of sequences on master |