From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | Luis Carril <luis(dot)carril(at)swarm64(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Option to dump foreign data in pg_dump |
Date: | 2019-06-28 15:20:58 |
Message-ID: | CAFj8pRAe-1RH=zpxce4yPoosPv3HEUNA1DBRk4gxkMQ-eUuExg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
pá 28. 6. 2019 v 17:17 odesílatel Daniel Gustafsson <daniel(at)yesql(dot)se>
napsal:
> > On 28 Jun 2019, at 16:49, Luis Carril <luis(dot)carril(at)swarm64(dot)com> wrote:
>
> > pg_dump ignores the dumping of data in foreign tables
> > on purpose, this patch makes it optional as the user maybe
> > wants to manage the data in the foreign servers directly from
> > Postgres. Opinions?
>
> Wouldn’t that have the potential to make restores awkward for FDWs that
> aren’t
> writeable? Basically, how can the risk of foot-gunning be minimized to
> avoid
> users ending up with dumps that are hard to restore?
>
It can be used for migrations, porting, testing (where FDW sources are not
accessible).
pg_dump has not any safeguards against bad usage. But this feature has
sense only if foreign tables are dumped as classic tables - so some special
option is necessary
Pavel
>
> cheers ./daniel
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-06-28 15:30:37 | Re: Option to dump foreign data in pg_dump |
Previous Message | Tom Lane | 2019-06-28 15:17:45 | Re: subscriptionCheck failures on nightjar |