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

From Fujii Masao
Subject Re: Streaming replication: sequences on slave seemingly ahead of sequences on master
Date
Msg-id CAHGQGwE_CdpEZu0TZ83oLuaQmvKbQXLU6x+YSPGgr3biUaujEg@mail.gmail.com
Whole thread Raw
In response to Re: Streaming replication: sequences on slave seemingly ahead of sequences on master  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Mon, May 7, 2012 at 10:33 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Simon Riggs <simon@2ndQuadrant.com> writes:
>> On 7 May 2012 09:01, Vincent de Phily <vincent.dephily@mobile-devices.fr> wrote:
>>> Would be nice to see it added to the documentation (unless I just didn't find
>>> it ?), as it is quite surprising, and might lead to problems if people expect
>>> to be able to read sequence values from the slave.
>
>> If you think so, please submit a patch. That's how it works here.
>
> Any documentation patch should be written by somebody who's actually
> researched the behavior a bit; in particular I believe this can be
> adjusted with the sequence CACHE setting.

No. That behavior is caused by the hard-coded value SEQ_LOG_VALS
(= 32 in sequence.c) rather than CACHE setting.

Regards,

--
Fujii Masao

pgsql-general by date:

Previous
From: Michael Nolan
Date:
Subject: Re: Streaming replication: sequences on slave seemingly ahead of sequences on master
Next
From: Merlin Moncure
Date:
Subject: Re: Streaming replication: sequences on slave seemingly ahead of sequences on master