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: oc logs $(oc get pods -o name -l strimzi.io/cluster=my-connect-cluster)
  ----
  
  .. Review the log output to verify that the initial snapshot has been executed. You should see something like this:
  +
  [source,shell,options="nowrap"]
  ----
  
negative.code: 
  . Create a `KafkaConnector` custom resource that configures your {prodname} PostgreSQL connector instance.
  +
  You configure a {prodname} PostgreSQL connector in a `.yaml` file that specifies the configuration properties for the connector.
  The 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.
  For the complete list of the configuration properties that you can set for the {prodname} PostgreSQL connector, see {link-prefix}:{link-postgresql-connector}#postgresql-connector-properties[PostgreSQL connector properties].
  +
  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.
  +
  