Re: Options OUTPUT_PLUGIN_* controlling format are confusing (Was: Misleading error message in logical decoding)

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Options OUTPUT_PLUGIN_* controlling format are confusing (Was: Misleading error message in logical decoding)
Date: 2014-09-30 05:44:10
Message-ID: CAB7nPqRfZVfN0=ZdL-bRt4MDa2QoGS=n7VB0EL=MKnw1CvD6mQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Sep 29, 2014 at 10:03 PM, Andres Freund <andres(at)2ndquadrant(dot)com>
wrote:

> > 3) The formulation here seems vague as a plugin that generates textual
> > output can call pg_logical_slot_peek_binary_changes as well:
>
> I've commented on this before: an output plugin doesn't call
> pg_logical_slot_peek_binary_changes - if at all it's the other way
> round.
>

Sorry. I am sure you got what I wanted to say: "a user can as well use
pg_logical_slot_peek_binary_changes to retrieve changes from a replication
slot that uses an plugin generating textual output" :)
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2014-09-30 05:45:11 Re: Options OUTPUT_PLUGIN_* controlling format are confusing (Was: Misleading error message in logical decoding)
Previous Message Atri Sharma 2014-09-30 05:40:42 Re: Proper query implementation for Postgresql driver