anchor.diff:  
   * {prodname} version
   * Connector type and name
  -* Database and table that contains the new row
  +* Database and table that contained the deleted row
   * Schema name
  -* If the event was part of a snapshot
  +* If the event was part of a snapshot (alwas `false` for _delete_ events)
   * ID of the transaction in which the operation was performed
   * Offset of the operation in the database log
   * Timestamp for when the change was made in the database
  
positive.code: [[postgresql-tombstone-events]]
  .Tombstone events
  When a row is deleted, the _delete_ event value still works with log compaction, because Kafka can remove all earlier messages that have that same key. However, for Kafka to remove all messages that have that same key, the message value must be `null`. To make this possible, the PostgreSQL connector follows a _delete_ event with a special _tombstone_ event that has the same key but a `null` value.
  
  // Type: reference
  // ModuleID: how-debezium-postgresql-connectors-map-data-types
  
negative.code: * Connector type and name
  * Database and table that contains the new row
  * Schema name
  * If the event was part of a snapshot (alwas `false` for _update_ events)
  * ID of the transaction in which the operation was performed
  * Offset of the operation in the database log
  * Timestamp for when the change was made in the database
  