Postgres Pro
Downloads
Home   >   mailing lists

Any objections to implementing LogicalDecodeMessageCB for pgoutput? - Mailing list pgsql-hackers

From Dave Cramer
Subject Any objections to implementing LogicalDecodeMessageCB for pgoutput?
Date
Msg-id CADK3HHJ-+9SO7KuRLH=9Wa1rAo60Yreq1GFNkH_kd0=CdaWM+A@mail.gmail.com
Whole thread Raw
Responses 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>)
List pgsql-hackers
Tree view
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 by date:

Previous
From: Tom Lane
Date:
Subject: Re: Making CASE error handling less surprising
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] Custom compression methods