Re: Sequences / Replication - Mailing list pgsql-general

From Jonathan Eastgate
Subject Re: Sequences / Replication
Date
Msg-id CAF0Mkq-uQTNz6ZgWT8FxQY3VKHk7cS2HfuthwEuGd6XQ5Av3TQ@mail.gmail.com
Whole thread Raw
In response to Sequences / Replication  (Jonathan Eastgate <jonathan.eastgate@simpro.co>)
Responses Re: Sequences / Replication  (Alvaro Aguayo Garcia-Rada <aaguayo@opensysperu.com>)
List pgsql-general
And further to my last post - another post in the forums related to this:


Thanks.

Jonathan J. Eastgate
Chief Technology Officer | simPRO Software Group
Ph: 1300 139 467    +61 7 3147 8777



Keep up to date with simPRO at: http://simprogroup.com/blog
The contents of this email are subject to our email disclaimer.


On Thu, Oct 20, 2016 at 6:03 PM, Jonathan Eastgate <jonathan.eastgate@simpro.co> wrote:
Hi everyone.

We're seeing some odd behaviour from a PostgreSQL group - one running as primary and the other as a hot slave using streaming replication.

When a failover event occurs and we switch to the hot slave as primary sequences in tables jump by 33 - so where the last number allocated in the sequence was 100 prior to failover once adding the next entry the sequence will produce the number 133. 


I've found the following post in the forums - but any advice on how to resolve or counter this would be appreciated.

Thanks in advance.


Jonathan J. Eastgate
Chief Technology Officer | simPRO Software Group
Ph: 1300 139 467    +61 7 3147 8777



Keep up to date with simPRO at: http://simprogroup.com/blog
The contents of this email are subject to our email disclaimer.



--

pgsql-general by date:

Previous
From: Jonathan Eastgate
Date:
Subject: Sequences / Replication
Next
From: "Jaisingkar, Piyush"
Date:
Subject: Unnest an array in postgresql