From: Scott Marlowe <scott.marlowe@gmail.com>
To: Guillaume Lelarge <guillaume@lelarge.info>
Cc: Tino Schwarze <postgresql@tisc.de>
Cc: pgsql-admin@postgresql.org
Subject: Re: Tuning postgres for fast restore?
Date: Sun, 22 Feb 2009 18:57:55 -0700
Message-ID: <dcc563d10902221757u31ea9e70g2eb57f9bc6a64e1e@mail.gmail.com> (raw)
In-Reply-To: <499FA9E7.1040109@lelarge.info>
References: <20090221004219.GA10127@easy2.in-chemnitz.de>
<499FA9E7.1040109@lelarge.info>
On Sat, Feb 21, 2009 at 12:14 AM, Guillaume Lelarge
<guillaume@lelarge.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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott.marlowe@gmail.com, guillaume@lelarge.info, postgresql@tisc.de
Subject: Re: Tuning postgres for fast restore?
In-Reply-To: <dcc563d10902221757u31ea9e70g2eb57f9bc6a64e1e@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox