anchor.diff:  ====
   *The issue we discuss below is already fixed in Debezium 1.0 and you should update as soon as possible*.
   
  -A new feature for skipping such unprocessable events is now merged as https://github.com/debezium/debezium/pull/1271[PR#1271] in the core Debezium framework and is available from version `1.1-next` onward.
  +A new feature for skipping such unprocessable events in general has been merged as https://github.com/debezium/debezium/pull/1271[PR#1271] in the core Debezium framework and will be part of the next Debezium 1.1 preview release.
   ====
   
   Two of the common things developers often fail to do are proper date-time handling and software version upgrades. Both of these can lead to issues on their own but makes things difficult when both occur together. We recently faced such an issue and provide a way to handle it. We'll start with some background on why this issue came up in the first place.
  
positive.code: 
  Debezium makes all of those above use-cases possible and very easy to build by providing a common platform and framework to connect our existing data sources like MongoDB, PostgreSQL or MySQL.
  
  This article is going to share our learnings with using Debezium on AWS RDS (AWS's managed database service) and hopefully help transfer some knowledge we've gained in that process and also document how to skip unparseable records from PostgreSQL's WAL when using a Debezium version older than `1.1-next` (see https://issues.redhat.com/browse/DBZ-1760[DBZ-1760]).
  
  Here's a brief architecture overview that shows a few of the use-cases that Debezium is powering and the general data platform.
  
  
negative.code: . Publish a message to Debezium's offset topic with the next LSN and TxId. We were able to successfully get it working by adding 1 to both the `lsn` and the `txId`.
  . Deploy Debezium again and it should have skipped the record.
  
  == Conclusion
  
  === Why Debezium?
  