From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | 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 09:36:40 |
Message-ID: | CA+U5nMJFbXQ=qmc2fvvmRHFOcOTMD0CUy2vz6BUjwBbR+dA2nA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 7 May 2012 09:19, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> On Mon, May 7, 2012 at 10:14 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> 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.
>
> FWIW, I think this would be a reasonable thing to document, given that
> it violates the principle of least surprise for people who are not
> intimately familiar with how replication and/or sequences work wrt wal
> logging in postgresql. (but no, I'm not actually volunteering at this
> point to write said patch due to my backlog already being too large
> :P)
Mine also. Its important that everybody understands that submitting a
patch is the way to get change, plus its a good test of whether the
change is actually worth the effort to make it happen.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | MD33 | 2012-05-07 12:33:46 | COPY column order |
Previous Message | Magnus Hagander | 2012-05-07 08:19:47 | Re: Streaming replication: sequences on slave seemingly ahead of sequences on master |