Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 1CF4D63888A for ; Sun, 22 Feb 2009 21:58:08 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 05840-01-9 for ; Sun, 22 Feb 2009 21:58:04 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mail.postgresql.org (Postfix) with ESMTP id 53831638B88 for ; Sun, 22 Feb 2009 21:57:57 -0400 (AST) Received: by yw-out-2324.google.com with SMTP id 5so688248ywh.73 for ; Sun, 22 Feb 2009 17:57:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=8oawGS4+d8t1yGsIUJigeOhfwDlzT7mSJFgLgEUF6lM=; b=A/m8P0El9Uke0c3IHd7qKwlVNm6hDrj4f14TCxWv43ODMCVSKTk9dcPs6kow283fXV 65GKgxIVByfvhCfT6m3SuoZ71eJXwbVqLE10+7dTK9jZwTDjS+UsNZP42Mc2I+sSLRoR jcWRWfRnJgWkVUyB4tNVPYLOngxZf007tBwgo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=UcB57FueyFDCSP8jJBjTkM0JTww9lZAx4m30WujKB/Xau0nVaZqeLu9pjz3VOmYHdE 5FUXI4Cc1qiFYmPHkzKnu8C7hSmeWqGEosqDB77+jeIBAmjlIJqfaby1NToWxWYb9sgW tEXvfCKyHTqvEGgu1YPLP9PbV+oU9PcGiOZMQ= MIME-Version: 1.0 Received: by 10.150.52.2 with SMTP id z2mr4812962ybz.128.1235354275663; Sun, 22 Feb 2009 17:57:55 -0800 (PST) In-Reply-To: <499FA9E7.1040109@lelarge.info> References: <20090221004219.GA10127@easy2.in-chemnitz.de> <499FA9E7.1040109@lelarge.info> Date: Sun, 22 Feb 2009 18:57:55 -0700 Message-ID: Subject: Re: Tuning postgres for fast restore? From: Scott Marlowe To: Guillaume Lelarge Cc: Tino Schwarze , pgsql-admin@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200902/190 X-Sequence-Number: 31411 On Sat, Feb 21, 2009 at 12:14 AM, Guillaume Lelarge wrote: > Tino Schwarze a =E9crit : >> [...] >> 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.