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

From Peter Eisentraut
Subject Re: Option to dump foreign data in pg_dump
Date
Msg-id 2a15ed10-77e3-5885-a247-e65b9e5e8407@2ndquadrant.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  (David Steele <david@pgmasters.net>)
Re: Option to dump foreign data in pg_dump  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On 2020-01-21 10:36, Luis Carril wrote:
>> Yes we can support --include-foreign-data without parallel option and
>> later add support for parallel option as a different patch.
> 
> Hi,
> 
>      I've attached a new version of the patch in which an error is 
> emitted if the parallel backup is used with the --include-foreign-data 
> option.

This seems like an overreaction.  The whole point of 
lockTableForWorker() is to avoid deadlocks, but foreign tables don't 
have locks, so it's not a problem.  I think you can just skip foreign 
tables in lockTableForWorker() using the same logic that getTables() uses.

I think parallel data dump would be an especially interesting option 
when using foreign tables, so it's worth figuring this out.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: making the backend's json parser work in frontend code
Next
From: Pavel Stehule
Date:
Subject: Re: [Proposal] Global temporary tables