From: | Luis Carril <luis(dot)carril(at)swarm64(dot)com> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Option to dump foreign data in pg_dump |
Date: | 2019-07-12 14:08:28 |
Message-ID: | LEJPR01MB0185EB194B0F4061E2B008F9E7F20@LEJPR01MB0185.DEUPRD01.PROD.OUTLOOK.DE |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > On 28 Jun 2019, at 19:55, Luis Carril <luis(dot)carril(at)swarm64(dot)com> wrote:
> > 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.
> I think this is a good option, the normal exclusion rules can then still apply
> in case not everything from a specific server is of interest.
Hi, here is a new patch to dump the data of foreign tables using pg_dump.
This time the user specifies for which foreign servers the data will be dumped, which helps in case of having a mix of writeable and non-writeable fdw in the database.
It would be nice to emit an error if the fdw is read-only, but that information is not available in the catalog.
Cheers
Luis M Carril
Attachment | Content-Type | Size |
---|---|---|
0001-Support-foreign-data-in-pg_dump.patch | text/x-patch | 7.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Nikolay Shaplov | 2019-07-12 14:13:43 | Re: [PATCH] get rid of StdRdOptions, use individual binary reloptions representation for each relation kind instead |
Previous Message | Fabien COELHO | 2019-07-12 13:58:21 | Re: Patch to document base64 encoding |