anchor.diff:  ----
   oc get kafkatopics
   ----
  -
  -.Results
  -
  -When the connector starts, it {link-prefix}:{link-postgresql-connector}#postgresql-snapshots[performs a consistent snapshot] of the PostgreSQL server databases that the connector is configured for. The connector then starts generating data change events for row-level operations and streaming change event records to Kafka topics.
   
   endif::product[]
   
  
positive.code: 
  . Create a `KafkaConnector` custom resource that configures your {prodname} PostgreSQL connector instance.
  +
  You configure a {prodname} PostgreSQL connector in a `.yaml` file that sets connector configuration properties. A connector configuration might instruct {prodname} to produce events for a subset of the schemas and tables, or it might set properties so that {prodname} ignores, masks, or truncates values in specified columns that are sensitive, too large, or not needed. See the {link-prefix}:{link-postgresql-connector}#postgresql-connector-properties[complete list of PostgreSQL connector properties] that can be specified in these configurations.
  +
  The following example configures a {prodname} connector that connects to a PostgreSQL server host, `192.168.99.100`, on port `5432`. This host has a database named `sampledb`, a schema named `public`, and `fulfillment` is the server's logical name.
  +
  
negative.code: ... INFO Snapshot is using user 'debezium' ...
  ----
  +
  If the connector starts correctly without errors, it creates a topic for each table whose changes the connector is capturing.
  For the example CR, there would be a topic for each table in the `public` schema.
  Downstream applications can subscribe to these topics.
  
  .. Verify that the connector created the topics by running the following command:
  +
  