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

From Daniel Gustafsson
Subject Re: Option to dump foreign data in pg_dump
Date
Msg-id F7E6CAAE-3358-4F29-A13F-55D008B50D35@yesql.se
Whole thread Raw
In response to Re: Option to dump foreign data in pg_dump  (Luis Carril <luis.carril@swarm64.com>)
Responses Re: Option to dump foreign data in pg_dump
List pgsql-hackers
> On 28 Jun 2019, at 17:30, Tom Lane <tgl@sss.pgh.pa.us> wrote:


> > Yeah, I think the feature as-proposed is a shotgun that's much more likely
> > to cause problems than solve them.  Almost certainly, what people would
> > really need is the ability to dump individual foreign tables' data not
> > everything.  (I also note that the main reason for "dump everything",
> > namely to get a guaranteed-consistent snapshot, isn't really valid for
> > foreign tables anyhow.)


I think this is sort of key here, the consistency guarantees are wildly
different.  A note about this should perhaps be added to the docs for the
option discussed here?

> On 28 Jun 2019, at 19:55, Luis Carril <luis.carril@swarm64.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
aconscious decision to dump the content of the foreign tables for a specific server, this would allow distinction if
multipleFDW 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.

cheers ./daniel


pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Re: [PATCH][PROPOSAL] Add enum releation option type
Next
From: Thomas Munro
Date:
Subject: Re: [HACKERS] advanced partition matching algorithm forpartition-wise join