Doc: fix typo in logicaldecoding.sgml.

There's no such field as OutputPluginOptions.output_mode;
it's actually output_type.  Noted by T. Katsumata.

Discussion: https://postgr.es/m/20170215072115.6101.29870@wrigleys.postgresql.org
This commit is contained in:
Tom Lane 2017-02-15 17:31:02 -05:00
parent f2ec57dee9
commit adb67d67f0
1 changed files with 1 additions and 1 deletions

View File

@ -419,7 +419,7 @@ CREATE TABLE another_catalog_table(data text) WITH (user_catalog_table = true);
data in a data type that can contain arbitrary data (e.g., <type>bytea</type>) is data in a data type that can contain arbitrary data (e.g., <type>bytea</type>) is
cumbersome. If the output plugin only outputs textual data in the cumbersome. If the output plugin only outputs textual data in the
server's encoding, it can declare that by server's encoding, it can declare that by
setting <literal>OutputPluginOptions.output_mode</> setting <literal>OutputPluginOptions.output_type</>
to <literal>OUTPUT_PLUGIN_TEXTUAL_OUTPUT</> instead to <literal>OUTPUT_PLUGIN_TEXTUAL_OUTPUT</> instead
of <literal>OUTPUT_PLUGIN_BINARY_OUTPUT</> in of <literal>OUTPUT_PLUGIN_BINARY_OUTPUT</> in
the <link linkend="logicaldecoding-output-plugin-startup">startup the <link linkend="logicaldecoding-output-plugin-startup">startup