Re: Option to dump foreign data in pg_dump - Mailing list pgsql-hackers

From Luis Carril
Subject Re: Option to dump foreign data in pg_dump
Date
Msg-id FRXPR01MB0182B04505ADB297D3C40EC0E7FC0@FRXPR01MB0182.DEUPRD01.PROD.OUTLOOK.DE
Whole thread Raw
In response to Re: Option to dump foreign data in pg_dump  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: Option to dump foreign data in pg_dump
List 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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Commitfest 2019-07, the first of five* for PostgreSQL 13
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Regression tests vs existing users in an installation