Any objections to implementing LogicalDecodeMessageCB for pgoutput?

From: Dave Cramer <davecramer(at)gmail(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Any objections to implementing LogicalDecodeMessageCB for pgoutput?
Date: 2020-07-24 15:33:52
Message-ID: CADK3HHJ-+9SO7KuRLH=9Wa1rAo60Yreq1GFNkH_kd0=CdaWM+A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2020-07-24 15:39:46 Re: [HACKERS] Custom compression methods
Previous Message Tom Lane 2020-07-24 15:22:10 Re: Making CASE error handling less surprising