Re: Tuning postgres for fast restore?

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Cc: Tino Schwarze <postgresql(at)tisc(dot)de>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Tuning postgres for fast restore?
Date: 2009-02-23 01:57:55
Message-ID: dcc563d10902221757u31ea9e70g2eb57f9bc6a64e1e@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Sat, Feb 21, 2009 at 12:14 AM, Guillaume Lelarge
<guillaume(at)lelarge(dot)info> wrote:
> Tino Schwarze a écrit :
>> [...]
>> I'm going to pg_restore a database dump of about 220 GiB (uncompressed,
>> but most data is BLOBs). The machine has 8 GiB of memory and 8 cores.
>> Is there any advice to speed up restoring, postgresql.conf-wise?
>>
>> I already have a script which does the data loading and index creation
>> in parallel. I'm looking for advice regarding shared_mem, work_mem and
>> maintenance_mem - shall I raise them?
>>
>
> You should definitely raise shared_buffers and maintenance_work_mem.

Also, you can disable fsync during a restore if the machine's not
handling any other databases.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Nicola Mauri 2009-02-23 08:59:10 Re: Crash with data corruption under Windows
Previous Message Tom Lane 2009-02-22 23:12:14 Re: database corruption help needed