> pg_dump ignores the dumping of data in foreign tables > on purpose, this patch makes it optional as the user maybe > wants to manage the data in the foreign servers directly from > Postgres. Opinions?
Wouldn’t that have the potential to make restores awkward for FDWs that aren’t writeable? Basically, how can the risk of foot-gunning be minimized to avoid users ending up with dumps that are hard to restore?
It can be used for migrations, porting, testing (where FDW sources are not accessible).
pg_dump has not any safeguards against bad usage. But this feature has sense only if foreign tables are dumped as classic tables - so some special option is necessary