Re: Option to dump foreign data in pg_dump
Luis Carril <luis.carril@swarm64.com>
From: Luis Carril <luis.carril@swarm64.com>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Daniel Gustafsson <daniel@yesql.se>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2019-06-28T17:55:52Z
Lists: pgsql-hackers
>Restoring content of FDW table via pg_restore or psql can be dangerous - there I see a risk, and can be nice to allow it only >with some form of safeguard. > >I think so important questions is motivation for dumping FDW - a) clonning (has sense for me and it is safe), b) real backup >(requires writeable FDW) - has sense too, but I see a possibility of unwanted problems. What about providing a list of FDW servers instead of an all or nothing option? In that way the user really has to do a conscious decision to dump the content of the foreign tables for a specific server, this would allow distinction if multiple FDW are being used in the same DB. Also I think it is responsability of the user to know if the FDW that are being used are read-only or not. Cheers Luis M Carril
Commits
-
pg_dump: Allow dumping data of specific foreign servers
- 2f9eb3132094 13.0 landed