Any objections to implementing LogicalDecodeMessageCB for pgoutput?

Поиск
Список
Период
Сортировка
От Dave Cramer
Тема Any objections to implementing LogicalDecodeMessageCB for pgoutput?
Дата
Msg-id CADK3HHJ-+9SO7KuRLH=9Wa1rAo60Yreq1GFNkH_kd0=CdaWM+A@mail.gmail.com
обсуждение исходный текст
Ответы Re: Any objections to implementing LogicalDecodeMessageCB for pgoutput?  (Andres Freund <andres@anarazel.de>)
Re: Any objections to implementing LogicalDecodeMessageCB for pgoutput?  (David Pirotte <dpirotte@gmail.com>)
Список pgsql-hackers
For logical replication there is no need to implement this, but others are using the pgoutput plugin for Change Data Capture. The reason they are using pgoutput is because it is guaranteed to be available as it is in core postgres. 

Implementing LogicalDecodeMessageCB provides some synchronization facility that is not easily replicated.

Thoughts ?

Dave Cramer

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Making CASE error handling less surprising
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] Custom compression methods