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: 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-18 15:21:10
Message-ID: CAB7nPqSFttjNB_2kAHa8OdNGJjvzakucGf24tsfkV-kRxqbo5g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 18, 2014 at 9:56 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> On 2014-09-18 09:50:38 -0500, Michael Paquier wrote:
>> > Do you see the difference between what your doc patch states and the
>> > explanation I've given nearby in this thread?
>> Perhaps that's the lack of documentation...
>
> Man. I've explained it to you about three times. The previous attempts
> at doing so didn't seem to help. If my explanations don't explain it so
> you can understand it adding them to the docs won't change a thing.
> That's why I ask whether you see the difference?
Urg sorry for the misunderstanding. The patch stated that this
parameter only influences the output of the SQL functions while it
defines if "the output plugin requires the output method to support
binary data"?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jehan-Guillaume de Rorthais 2014-09-18 16:07:34 BUG: *FF WALs under 9.2 (WAS: .ready files appearing on slaves)
Previous Message Andres Freund 2014-09-18 14:56:58 Re: Options OUTPUT_PLUGIN_* controlling format are confusing (Was: Misleading error message in logical decoding)