postgres.git / summary / log / commit / refs

commit    19c324d9fb4d59db1d0c3e8865356fb6867dc35e
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Wed Feb 15 22:31:02 2017 +0000

    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


 doc/src/sgml/logicaldecoding.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/src/sgml/logicaldecoding.sgml b/doc/src/sgml/logicaldecoding.sgml
index 2fbcdc15ab0..b65de324f53 100644
--- a/doc/src/sgml/logicaldecoding.sgml
+++ b/doc/src/sgml/logicaldecoding.sgml
@@ -404,7 +404,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


[parent: d0e9c0e3199c]