pglogical Replication CONFLICT

Поиск
Список
Период
Сортировка
От Steven Forrester
Тема pglogical Replication CONFLICT
Дата
Msg-id DB5PR07MB08695897799BD647D33D0F098CEA0@DB5PR07MB0869.eurprd07.prod.outlook.com
обсуждение исходный текст
Список pgsql-general
I am using PostgreSQL 9.4 with pglogical replication. I have 1 provider node and 1 subscriber in 2 separate locations. The subscriber subscribes to 1 database on the provider. Every evening a function runs that DELETE's & INSERT's to tables that are replicated to the subscriber and causes CONFLICT messages to be logged:-

CONFLICT: remote UPDATE on relation db1.schedule. Resolution: (null).
CONFLICT: remote UPDATE on relation db1.schedule (tuple not found). Resolution: skip.

When I run the individual DELETE & INSERT statements to the schedule table manually I don't get any conflicts.

I have also compared the provider and subscribers data and they appear to be consistent with each other.

Any help or suggestions would be much appreciated.

В списке pgsql-general по дате отправления:

Предыдущее
От: Andreas Joseph Krogh
Дата:
Сообщение: ON CONFLICT does not support deferrable unique constraints
Следующее
От: Scott Marlowe
Дата:
Сообщение: Re: ON CONFLICT does not support deferrable unique constraints