In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

When trying Debezium Server on GCP CloudSQL I get a log of warnings about types being already mapped. I would like to know why and what are the consequences of those warnings.

For example:

2024-12-16 13:41:56,337 WARN  [io.deb.con.pos.TypeRegistry] (pool-8-thread-1) Type [oid:3343536, name:table1] is already mapped

I have multiple schemas containing the same tables, so of course table1 is present in all those schemas (one for each tenant), For example:

schema1/table1

schema2/table1

...

In config/application.properties I have set:

 
debezium.source.schema.include.list=schema1
 
... this was set in the hope that Debezium will only look at schema1, but it still prints those warnings.

What Debezium connector do you use and what version?

The postgres connector bundled in debezium-server-dist-3.0.4.Final.tar.gz, debezium-connector-postgres-3.0.4.Final

What is the connector configuration?

debezium.source.plugin.name=pgoutput
debezium.source.connector.class=io.debezium.connector.postgresql.PostgresConnector
debezium.source.offset.storage.file.filename=data/offsets.dat
debezium.source.offset.flush.interval.ms=0
debezium.source.database.hostname=db.host.com
debezium.source.database.port=5432
debezium.source.database.user=user
debezium.source.database.password=123
debezium.source.database.dbname=db
debezium.source.topic.prefix=debezium
debezium.source.schema.include.list=schema1

What is the captured database version and mode of deployment?

GCP CloudSQL, postgresql 13

What behavior do you expect?

Would like to get rid of the warnings.

What behavior do you see?

Getting the warning about types being already mapped.

Do you see the same behaviour using the latest released Debezium version?

This is the latest release.

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

Tried trace logging, but there's no additional info besides the WARN messages.

How to reproduce the issue using our tutorial deployment?

I just used run.sh

Feature request or enhancement

-

Which use case/requirement will be addressed by the proposed feature?

-

Implementation ideas (optional)

<Your answer>