anchor.diff:  This name is used as the prefix for all Kafka topics that receive change event records.
   <6> Changes in only the `public.inventory` schema are captured.
   
  +. Register your connector instance with Kafka Connect. For example, if you saved your `KafkaConnector` resource in the `inventory-connector.yaml` file, you would run the following command: 
  ++
  +[source,shell,options="nowrap"]
  +----
  +oc apply -f inventory-connector.yaml
  +----
  ++
  +This registers `inventory-connector` and the connector starts to run against the `inventory` database.
  +
  +. Verify that the connector was created and has started: 
  +.. Display the Kafka Connect log output to verify that the connector was created and has started to capture changes in the specified database:
  ++
  +[source,shell,options="nowrap"]
  +----
  +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"]
  +----
  +... INFO Starting snapshot for ...
  +... INFO Snapshot is using user 'debezium' ... 
  +----
  +
  +.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[]
   
  +ifdef::community[]
  +
  +// Type: concept
  +// ModuleID:debezium-postgresql-connector-configuration-example
  +// Title: {prodname} PostgreSQL connector configuration example
  +[[postgresql-example-configuration]]
  +=== Connector configuration example
  +
  +Following is an example of the configuration for a PostgreSQL connector that connects to a PostgreSQL server on port 5432 at 192.168.99.100, whose logical name is `fullfillment`. Typically, you configure the {prodname} PostgreSQL connector in a `.json` file using the configuration properties available for the connector.
  +
  +You can choose to produce events for a subset of the schemas and tables. Optionally, ignore, mask, or truncate columns that are sensitive, too large, or not needed.
  +
  +[source,json]
  +----
  +{
  +  "name": "inventory-connector",  // <1>
  +  "config": {
  +    "connector.class": "io.debezium.connector.postgresql.PostgresConnector", // <2>
  +    "database.hostname": "192.168.99.100", // <3>
  +    "database.port": "5432", // <4>
  +    "database.user": "postgres", // <5>
  +    "database.password": "postgres", // <6>
  +    "database.dbname" : "postgres", // <7>
  +    "database.server.name": "fullfillment", // <8>
  +    "table.include.list": "public.inventory" // <9>
  +
  +  }
  +}
  +----
  +<1> The name of the connector when registered with a Kafka Connect service.
  +<2> The name of this PostgreSQL connector class.
  +<3> The address of the PostgreSQL server.
  +<4> The port number of the PostgreSQL server.
  +<5> The name of the PostgreSQL user that has the {link-prefix}:{link-postgresql-connector}#postgresql-permissions[required privileges].
  +<6> The password for the PostgreSQL user that has the {link-prefix}:{link-postgresql-connector}#postgresql-permissions[required privileges].
  +<7> The name of the PostgreSQL database to connect to
  +<8> The logical name of the PostgreSQL server/cluster, which forms a namespace and is used in all the names of the Kafka topics to which the connector writes, the Kafka Connect schema names, and the namespaces of the corresponding Avro schema when the Avro converter is used.
  +<9> A list of all tables hosted by this server that this connector will monitor. This is optional, and there are other properties for listing the schemas and tables to include or exclude from monitoring.
  +
   See the {link-prefix}:{link-postgresql-connector}#postgresql-connector-properties[complete list of PostgreSQL connector properties] that can be specified in these configurations.
   
   You can send this configuration with a `POST` command to a running Kafka Connect service. The service records the configuration and starts the connector task that connects to the PostgreSQL database and streams change event records to Kafka topics.
   
  -// Type: procedure
  -// ModuleID: adding-debezium-postgresql-connector-configuration-to-kafka-connect
  -// Title: Adding {prodname} PostgreSQL connector configuration to Kafka Connect
   [[postgresql-adding-connector-configuration]]
   === Adding connector configuration
   
  -ifdef::community[]
   To start running a PostgreSQL connector, create a connector configuration and add the configuration to your Kafka Connect cluster. 
   
   .Prerequisites
  
positive.code: // Type: assembly
  [id="debezium-connector-for-postgresql"]
  = {prodname} connector for PostgreSQL
  
  ifdef::community[]
  
  
negative.code: . Use the link:{link-kafka-docs}/#connect_rest[Kafka Connect REST API] to add that connector configuration to your Kafka Connect cluster. 
  
  endif::community[]
  
  // Type: reference
  // ModuleID: descriptions-of-debezium-postgresql-connector-configuration-properties
  