anchor.diff:  ----
   <1> Set up a state store for storing the latest `biography` value per customer id
   <2> The actual streaming pipeline: for each message on the customers topic, apply the logic for replacing the TOAST column marker value and write the transformed message to an output topic
  -<3> Check wether the `biography` value from the incoming message is the marker
  +<3> Check whether the `biography` value from the incoming message is the marker
   <4> If so, get the current `biography` value for the customer from the state store
   <5> Replace the marker value with the actual value obtained from the state store
   <6> If the incoming message has an actual `biography` value, put this to the state store
  
positive.code: No, TOAST!
  
  So what's that?
  https://www.postgresql.org/docs/current/storage-toast.html[TOAST] (The Oversized-Attribute Storage Technique) is a mechanism in Postgres which allows to store large column values in multiple physical rows, circumventing the page size limit of 8 KB.
  
  ++++
  <div class="imageblock centered-image">
  
negative.code: 
  One interesting variation of the "ignore" approach is the usage of triggers in the sink database:
  registered for the column that may receive the marker value, they can "veto" such change and just keep the previously stored value instead.
  The following shows an example of such a trigger in Postgres:
  
  [source,sql]
  ----
  