Re: parallel pg_restore - WIP patch

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: parallel pg_restore - WIP patch
Date: 2008-09-26 12:37:26
Message-ID: 48DCD786.2020105@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stefan Kaltenbrunner wrote:
> Andrew Dunstan wrote:
>>
>> Attached is my WIP patch for parallel pg_restore. It's still very
>> rough, but seems to work.
>>
>> Anyone who can test this with highend equipment would be helping some.
>
> tried playing with this(on a 22Gb compressed dump using 4 connections)
> but it does not seem to work at all for me:
>
> pg_restore: [custom archiver] out of memory
> pg_restore: [custom archiver] could not uncompress data: invalid block
> type
> pg_restore: [custom archiver] out of memory
> pg_restore: [custom archiver] could not uncompress data: invalid
> stored block lengths
> pg_restore: [custom archiver] out of memory
> pg_restore: [custom archiver] out of memory
> pg_restore: [custom archiver] could not uncompress data: invalid
> distance too far back
> pg_restore: [custom archiver] could not uncompress data: invalid
> distances set
> pg_restore: [custom archiver] could not uncompress data: invalid code
> lengths set
> pg_restore: [custom archiver] could not uncompress data: incorrect
> data check
> pg_restore: [custom archiver] could not uncompress data: invalid code
> lengths set
> pg_restore: [custom archiver] out of memory
> pg_restore: [custom archiver] out of memory
> pg_restore: [custom archiver] out of memory
> pg_restore: [custom archiver] out of memory
> pg_restore: [custom archiver] could not uncompress data: invalid
> literal/length code
> pg_restore: [custom archiver] could not uncompress data: invalid
> literal/length code
> pg_restore: [custom archiver] could not uncompress data: invalid block
> type
>
> each pg_restore process seem to eat a few gigabytes of memory in a few
> seconds.

Ouch. Ok, Thanks for the report. I will investigate.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas OSB sIT 2008-09-26 12:43:42 Re: Updates of SE-PostgreSQL 8.4devel patches
Previous Message D'Arcy J.M. Cain 2008-09-26 12:37:20 Re: Proposal: new border setting in psql