anchor.diff:  |`plugin.name` +
   0.7.0 and later
   |`decoderbufs`
  -|The name of the Postgres link:#output-plugin[logical decoding plugin] installed on the server. Supported values are either `decoderbufs`, `wal2json` or `wal2json_rds`. +
  +|The name of the Postgres link:#output-plugin[logical decoding plugin] installed on the server. Supported values are either `decoderbufs`, `wal2json`, `wal2json_rds`, or `pgoutput`. +
   There are two new options supported since 0.8.0.Beta1
   
   * `wal2json_streaming`
   * `wal2json_rds_streaming`.
  +
  +There is a new option supported since 0.10.0.Beta3
  +
  +* `pgoutput`
   
   When the processed transactions are very large it is possible that the `JSON` batch event with all changes in the transaction will not fit into the hard-coded memory buffer of size 1 GB.
   In such cases it is possible to switch to so-called *streaming* mode when every change in transactions is sent as a separate message from PostgreSQL into Debezium.
  
positive.code: [[setting-up-PostgreSQL]]
  == Setting up PostgreSQL
  
  Before using the Debezium PostgreSQL connector to monitor the changes committed on a PostgreSQL server, first install the logical decoding plugin into the PostgreSQL server, enable a replication slot, and configure a user with sufficient privileges to perform the replication.
  
  Note that *if your database is hosted by a service* such as https://www.heroku.com/postgres[Heroku Postgres] you may be unable to install the plugin. If so, you'll be unable to monitor your database with Debezium.
  
  [[amazon-rds]]
  === PostgreSQL on Amazon RDS
  
negative.code: Also see link:/docs/install/postgres-plugins/[Logical Decoding Output Plug-in Installation for PostgreSQL] for more detailed instructions of setting up and testing logical decoding plug-ins.
  ====
  
  [NOTE]
  ====
  As of Debezium 0.10, the connector now supports PostgreSQL 10+ logical replication streaming using _pgoutput_.  This means that a logical decoding output plug-in is no longer necessary and changes can be emited directly from the replication stream by the connector.
  ====
  As of PostgreSQL 9.4, the only way to read changes to the write-ahead-log is to first install a logical decoding output plugin. Plugins are written in C, compiled, and installed on the machine which runs the PostgreSQL server. Plugins use  a number of PostgreSQL specific APIs, as described by the https://www.postgresql.org/docs/9.6/static/logicaldecoding-output-plugin.html[_PostgreSQL documentation_].
  
  Debezium's PostgreSQL connector works with one of Debezium's supported logical decoding plugin to encode the changes in either https://github.com/google/protobuf[_Protobuf format_] or http://www.json.org/[_JSON_] format.
  