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

<div dir="ltr"><br /><div class="gmail_extra"><br /><div class="gmail_quote">On Tue, Sep 30, 2014 at 12:06 AM, Robert
Haas<span dir="ltr"><<a href="mailto:robertmhaas@gmail.com" target="_blank">robertmhaas@gmail.com</a>></span>
wrote:<br/><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">OnMon, Sep 29, 2014 at 9:03 AM, Andres Freund <<a
href="mailto:andres@2ndquadrant.com">andres@2ndquadrant.com</a>>wrote:<br /> >> -        except that changes
arereturned as <type>bytea</type>.<br /> >> +        except that changes are returned as
<type>bytea</type>and that it<br /> >> can<br /> >> +        be used on slots using output
pluginsthat only support binary<br /> >> output.<br /> ><br /> > Imo that's pretty much implied because it
referencesthe !binary<br /> > version. But I guess it doesn't hurt to be explicit. How about:<br /> > " ... on
outputplugins using any form of output, including binary."?<br /><br /></span>I think you should just leave it alone. 
There'sno problem with what<br /> it says there right now.  It goes without saying that if the plugin<br /> can only
returnbytea, then you have to use the bytea-returning<br /> function to get it.  If it's not clear that such plugins
mightexist,<br /> that needs to be clarified better elsewhere, not here.<span class="HOEnZb"><font color="#888888"><br
/></font></span></blockquote></div>Yes,not modifying the current text would be fine.<br />-- <br />Michael<br
/></div></div>