From: Tom Lane <tgl@sss.pgh.pa.us>
To: Shridhar Daithankar <ghodechhap@ghodechhap.net>
Cc: grupos@carvalhaes.net
Cc: pgsql-general@postgresql.org
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] pg_restore taking 4 hours!
Date: Wed, 01 Dec 2004 10:38:37 -0500
Message-ID: <8361.1101915517@sss.pgh.pa.us> (raw)
In-Reply-To: <200412011955.23543.ghodechhap@ghodechhap.net>
References: <41ADA82A.7070405@carvalhaes.net>
<200412011955.23543.ghodechhap@ghodechhap.net>
Shridhar Daithankar <ghodechhap@ghodechhap.net> writes:
> On Wednesday 01 Dec 2004 4:46 pm, Rodrigo Carvalhaes wrote:
>> I need to find a solution for this because I am convincing customers
>> that are using SQL Server, DB2 and Oracle to change to PostgreSQL but
>> this customers have databases of 5GB!!! I am thinking that even with a
>> better server, the restore will take 2 days!
> Can you try bumping sort mem lot higher(basically whatever the machine can
> afford) so that index creation is faster?
It would be a good idea to bump up vacuum_mem as well. In current
sources it's vacuum_mem (well actually maintenance_work_mem) that
determines the speed of CREATE INDEX; I forget just how long that
behavior has been around, but 7.4.6 might do it too.
regards, tom lane
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-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, ghodechhap@ghodechhap.net, grupos@carvalhaes.net, pgsql-general@postgresql.org
Subject: Re: [PERFORM] pg_restore taking 4 hours!
In-Reply-To: <8361.1101915517@sss.pgh.pa.us>
* 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