Skip site navigation (1) Skip section navigation (2)

Re: Restore of pg_dump taking a long time...

From: Jim Nasby <jnasby(at)pervasive(dot)com>
To: Todd A(dot) Cook <tcook(at)blackducksoftware(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ruairi <rcarroll(at)bluemetrix(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Restore of pg_dump taking a long time...
Date: 2006-05-25 20:51:54
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
On May 24, 2006, at 2:56 PM, Todd A. Cook wrote:

> Tom Lane wrote:
>> "Todd A. Cook" <tcook(at)blackducksoftware(dot)com> writes:
>>> I have found that increasing maintenance_work_mem can decrease index
>>> build speed on large tables:
>> You should probably re-measure when 8.2 comes out; we've fixed a  
>> number
>> of performance issues in the sorting code that might cause that.
> Thanks.  I'll do that.  If I can, I'll try it sooner on a build
> from CVS.

If you'll be messing around with CVS, you might also want to try this  
(which was written by someone else). It hacks compression into the on- 
disk sort code, which has shown a 50% speed improvement on my  
machine. It should be fine to use for loading a database, but you  
wouldn't want to leave it in for serious use (IIRC there's some cases  
it flat-out doesn't handle right now).

You could probably apply that to 8.1.4 as well if you wanted to; it  
should be fine for just loading the database.
Jim C. Nasby, Sr. Engineering Consultant      jnasby(at)pervasive(dot)com
Pervasive Software    work: 512-231-6117
vcard:       cell: 512-569-9461

In response to

pgsql-admin by date

Next:From: Jim NasbyDate: 2006-05-25 20:55:25
Subject: Re: How to mesure transaction rate in Postgres
Previous:From: Alvaro HerreraDate: 2006-05-25 20:43:19
Subject: Re: pg_clog questions

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group