If the table 't3' does not exist in the remote DSN, the SELECT
query returns an error:
It should return an empty set.
It does not seem to be useful to send a warning (instead of the error) on every SELECT.
But sending a warning at CREATE TABLE time could probably be useful, to make
the user aware that there is no such table on the remoter data source.