anchor.diff:  so the structure of transaction events or other details may still change as development progresses.
   ====
   
  -Debezium can generate events that represents tranaction metadata boundaries and enrich data messages.
  +Debezium can generate events that represents transaction metadata boundaries and enrich data messages.
   
   ==== Transaction boundaries
   Debezium generates events for every transaction start and end.
  
positive.code: So far these differences have been identified:
  
  * wal2json plug-in is not able to process quoted identifiers (https://github.com/eulerto/wal2json/issues/35[issue])
  * wal2json plug-in does not emit events for tables without primary keys
  * wal2json plug-in does not support special values (`NaN` or `infinity`) for floating point types
  * wal2json should be used with setting the `schema.refresh.mode` connector option to `columns_diff_exclude_unchanged_toast`;
  otherwise, when receiving a change event for a row containing an unchanged TOAST column, no field for that column will be contained in the emitted change event's `after` structure.
  
negative.code: The requirement for adding this is tracked under the wal2json https://github.com/eulerto/wal2json/issues/98[issue 98].
  See the documentation of `columns_diff_exclude_unchanged_toast` further below for implications of using it.
  
  * pgoutput plug-in does not emit all the events for tables without primary keys, it only emits inserts
  
  All up-to-date differences are tracked in a test suite https://github.com/debezium/debezium/blob/master/debezium-connector-postgres/src/test/java/io/debezium/connector/postgresql/DecoderDifferences.java[Java class].
  
  