anchor.diff:  [id="postgresql-hstore-type"]
   === HSTORE type
   
  -When the `hstore.handling.mode` connector configuration property is set to `json` (the default), the connector represents `HSTORE` values as string representations of JSON values and encodes them as shown in the following table. When the `hstore.handling.mode` property is set to `map`, the connector uses the `MAP` schema type for `HSTORE` values.
  +The setting of the PostgreSQL connector configuration property xref:postgresql-property-hstore-handling-mode[`hstore.handling.mode`] determines how the connector maps `HSTORE` values.
  +
  +When the `dhstore.handling.mode` property is set to `json` (the default), the connector represents `HSTORE` values as string representations of JSON values and encodes them as shown in the following table. When the `hstore.handling.mode` property is set to `map`, the connector uses the `MAP` schema type for `HSTORE` values.
   
   .Mappings for `HSTORE` data type
   [cols="25%a,20%a,55%a",options="header"]
  
positive.code: [id="postgresql-temporal-types"]
  === Temporal types
  
  Other than PostgreSQL's `TIMESTAMPTZ` and `TIMETZ` data types, which contain time zone information, how temporal types are mapped depends on the value of the `time.precision.mode` connector configuration property. The following sections describe these mappings:
  
  * xref:postgresql-time-precision-mode-adaptive[`time.precision.mode=adaptive`]
  * xref:postgresql-time-precision-mode-adaptive-time-microseconds[`time.precision.mode=adaptive_time_microseconds`]
  
negative.code: |`org.apache.kafka.connect.data.Decimal` +
   +
  The `scale` schema parameter contains an integer representing how many digits the decimal point was shifted.
  The `scale` schema parameter is determined by the xref:postgresql-property-money-fraction-digits[`money.fraction.digits`] connector configuration property.
  
  |===
  
  