DanielLeens commented on issue #8184: URL: https://github.com/apache/seatunnel/issues/8184#issuecomment-4671706377
Thanks for reporting this. I checked the current Postgres CDC discovery path, and this looks like a real connector-side bug rather than just harmless noisy logging. Right now `TableDiscoveryUtils.listTables()` first reads *all* database names from `pg_database`, then it tries to query `"<db>".INFORMATION_SCHEMA.TABLES` for each one, and only after that applies the configured table filter. So a config like `database-names = [\"postgres\"]` does not actually prevent those cross-database probes from happening. That matches the warnings you posted: the filter is being applied too late in the flow, after the connector has already tried to inspect the other databases. I do not see a clean config-only switch in the current implementation that avoids this properly. The correct fix direction is to restrict the database iteration before issuing those per-database queries, instead of treating the cross-database failures as expected warnings. This issue is worth keeping open as a real bug. We've already marked it as `help wanted`, so a focused PR would be very welcome. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
