Re: parallel pg_restore - WIP patch

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Russell Smith <mr-russ(at)pws(dot)com(dot)au>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Jeffrey Baker <jwbaker(at)gmail(dot)com>
Subject: Re: parallel pg_restore - WIP patch
Date: 2008-09-29 13:02:38
Message-ID: 48E0D1EE.9010504@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-09-29 13:17:12 Re: parallel pg_restore - WIP patch
Previous Message Markus Wanner 2008-09-29 12:54:10 Re: Proposal: move column defaults into pg_attribute along with attacl