The following bug has been logged on the website:
Bug reference: 17328
Logged by: Mark Jones
Email address: boatcoder@gmail.com
PostgreSQL version: 14.0
Operating system: MacOS (but not important)
Description:
With a statement like:
`import foreign schema "public" limit to (public.segment_over_1) from
server metrics into public;`
You never get an error, even if that table does not exist on the FDW server.
This makes it a multi-step process to find out if what you told Postgres to
do was actually done. You have to import the schema, then check for the
existence of the table. Seems like this should create an error if the
remote table does not exist.
In my case it was during unit test where Django was creating the server
during a migration and then changing the db name to start with test_. Then
my code internal to the application was trying to import the schema from the
wrong server. I'm a bit embarrassed how long it took me figure out what was
going on, but a simple error during the import would have made it very
obvious.