| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Vincent de Phily <vincent(dot)dephily(at)mobile-devices(dot)fr>, 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-07 13:59:24 |
| Message-ID: | CAHGQGwE_CdpEZu0TZ83oLuaQmvKbQXLU6x+YSPGgr3biUaujEg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, May 7, 2012 at 10:33 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
>> On 7 May 2012 09:01, Vincent de Phily <vincent(dot)dephily(at)mobile-devices(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2012-05-07 14:05:13 | Re: Streaming replication: sequences on slave seemingly ahead of sequences on master |
| Previous Message | Michael Nolan | 2012-05-07 13:52:56 | Re: Streaming replication: sequences on slave seemingly ahead of sequences on master |