Sequences / Replication

Поиск
Список
Период
Сортировка
От Jonathan Eastgate
Тема Sequences / Replication
Дата
Msg-id CAF0Mkq_M06-A=cwbZECEPFg9J36PX6dg-mc9-RcC46jhsDzk4w@mail.gmail.com
обсуждение исходный текст
Ответы Re: Sequences / Replication  (Jonathan Eastgate <jonathan.eastgate@simpro.co>)
Re: Sequences / Replication  (Albe Laurenz <laurenz.albe@wien.gv.at>)
Список pgsql-general
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 по дате отправления:

Предыдущее
От: "David G. Johnston"
Дата:
Сообщение: Re: Selecting records with highest timestamp - for a join
Следующее
От: Jonathan Eastgate
Дата:
Сообщение: Re: Sequences / Replication