Re: Options OUTPUT_PLUGIN_* controlling format are confusing (Was: Misleading error message in logical decoding) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Options OUTPUT_PLUGIN_* controlling format are confusing (Was: Misleading error message in logical decoding)
Date
Msg-id CA+TgmoYr=t1eEqm0VWsEKmNLDuw-w0w2j3JL3JBViOz+BhML0g@mail.gmail.com
Whole thread Raw
In response to Re: Options OUTPUT_PLUGIN_* controlling format are confusing (Was: Misleading error message in logical decoding)  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Options OUTPUT_PLUGIN_* controlling format are confusing (Was: Misleading error message in logical decoding)  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Mon, Sep 29, 2014 at 9:03 AM, Andres Freund <andres@2ndquadrant.com> wrote:
>> -        except that changes are returned as <type>bytea</type>.
>> +        except that changes are returned as <type>bytea</type> and that it
>> can
>> +        be used on slots using output plugins that only support binary
>> output.
>
> Imo that's pretty much implied because it references the !binary
> version. But I guess it doesn't hurt to be explicit. How about:
> " ... on output plugins using any form of output, including binary."?

I think you should just leave it alone.  There's no problem with what
it says there right now.  It goes without saying that if the plugin
can only return bytea, then you have to use the bytea-returning
function to get it.  If it's not clear that such plugins might exist,
that needs to be clarified better elsewhere, not here.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [REVIEW] Re: Compression of full-page-writes
Next
From: Robert Haas
Date:
Subject: Re: [v9.5] Custom Plan API