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

From vignesh C
Subject Re: Option to dump foreign data in pg_dump
Date
Msg-id CALDaNm1gVyCh1wW9i3a6v5dthctE+3mB20B666X=G2vX3Q1HVw@mail.gmail.com
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  (Luis Carril <luis.carril@swarm64.com>)
List pgsql-hackers
On Mon, Jan 20, 2020 at 8:34 PM Luis Carril <luis.carril@swarm64.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
skippingthe 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



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Physical replication slot advance is not persistent
Next
From: Amit Kapila
Date:
Subject: Re: Error message inconsistency