Re: parallel pg_restore - WIP patch - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: parallel pg_restore - WIP patch
Date
Msg-id 48E0D1EE.9010504@dunslane.net
Whole thread Raw
In response to Re: parallel pg_restore - WIP patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: parallel pg_restore - WIP patch  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>   
>> Tom Lane wrote:
>>     
>>> Hmm, I'll bet the restore code doesn't realize that this can't run in
>>> parallel with index creation on either table ...
>>>       
>
>   
>> Yeah. Of course, it's never needed to bother with stuff like that till now.
>>     
>
>   
>> The very simple fix is probably to run a separate parallel cycle just 
>> for FKs, after the index creation.
>>     
>
> Um, FKs could conflict with each other too, so that by itself isn't
> gonna fix anything.
>
>             
>   

Good point. Looks like we'll need to make a list of "can't run in 
parallel with" items as well as strict dependencies.

cheers

andrew


pgsql-hackers by date:

Previous
From: Markus Wanner
Date:
Subject: Re: Proposal: move column defaults into pg_attribute along with attacl
Next
From: Tom Lane
Date:
Subject: Re: parallel pg_restore - WIP patch