Skip site navigation (1) Skip section navigation (2)

Re: parallel pg_restore - WIP patch

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, 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 19:54:42
Message-ID: 48E13282.5030605@kaltenbrunner.cc (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> Tom Lane wrote:
>>> 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.
> 
> Yeah, I was just thinking about that.  The current archive format
> doesn't really carry enough information for this.  I think there
> are two basic solutions we could adopt:
> 
> * Extend the archive format to provide some indication that "restoring
> this object requires exclusive access to these dependencies".
> 
> * Hardwire knowledge into pg_restore that certain types of objects
> require exclusive access to their dependencies.
> 
> The former seems more flexible, as well as more in tune with the basic
> design assumption that pg_restore shouldn't have a lot of knowledge
> about individual archive object types.  But it would mean that you
> couldn't use parallel restore with any pre-8.4 dumps.  In the long run
> that's no big deal, but in the short run it's annoying.

hmm not sure how much of a problem that really is - we usually recommend 
to use the pg_dump version of the target database anyway.




Stefan

In response to

Responses

pgsql-hackers by date

Next:From: postgres Emanuel CALVO FRANCODate: 2008-09-29 21:27:51
Subject: Re: [HACKERS] PostgreSQL future ideas
Previous:From: Zdenek KotalaDate: 2008-09-29 19:42:50
Subject: pg_upgrade performance test

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group