diff options
author | Tom Lane | 2017-02-15 22:31:02 +0000 |
---|---|---|
committer | Tom Lane | 2017-02-15 22:31:02 +0000 |
commit | adb67d67f0f29acb175620ab05be26a146512fa2 (patch) | |
tree | 6ce1bfa5a672669e582f78b9c14b27ab2ad94e0e | |
parent | f2ec57dee93b29e2e27235ec8cc0683d0bc7d775 (diff) |
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/[email protected]
-rw-r--r-- | doc/src/sgml/logicaldecoding.sgml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/logicaldecoding.sgml b/doc/src/sgml/logicaldecoding.sgml index c4dff3b9ff..6e7517d04d 100644 --- a/doc/src/sgml/logicaldecoding.sgml +++ b/doc/src/sgml/logicaldecoding.sgml @@ -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 cumbersome. If the output plugin only outputs textual data in the 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 of <literal>OUTPUT_PLUGIN_BINARY_OUTPUT</> in the <link linkend="logicaldecoding-output-plugin-startup">startup |