| From: | vignesh C <vignesh21(at)gmail(dot)com> |
|---|---|
| To: | Luis Carril <luis(dot)carril(at)swarm64(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Option to dump foreign data in pg_dump |
| Date: | 2020-01-21 05:16:29 |
| Message-ID: | CALDaNm1gVyCh1wW9i3a6v5dthctE+3mB20B666X=G2vX3Q1HVw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 20, 2020 at 8:34 PM Luis Carril <luis(dot)carril(at)swarm64(dot)com> wrote:
>
>
> Hi Vignesh,
>
> yes you are right I could reproduce it also with 'file_fdw'. The issue is that LOCK is not supported on foreign tables, so I guess that the safest solution is to make the --include-foreign-data incompatible with --jobs, because skipping the locking for foreign tables maybe can lead to a deadlock anyway. Suggestions?
>
Yes we can support --include-foreign-data without parallel option and
later add support for parallel option as a different patch.
Regards,
Vignesh
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2020-01-21 05:19:46 | Re: Error message inconsistency |
| Previous Message | Michael Paquier | 2020-01-21 05:07:30 | Re: Physical replication slot advance is not persistent |