Re: Option to dump foreign data in pg_dump

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Luis Carril <luis(dot)carril(at)swarm64(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Option to dump foreign data in pg_dump
Date: 2019-07-01 09:29:54
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> On 28 Jun 2019, at 17:30, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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(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.

cheers ./daniel

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2019-07-01 09:49:13 Re: [HACKERS] advanced partition matching algorithm for partition-wise join
Previous Message Thomas Munro 2019-07-01 09:25:30 Re: Re: [PATCH][PROPOSAL] Add enum releation option type