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

Re: 7 hrs for a pg_restore?

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Douglas J Hunley" <doug(at)hunley(dot)homeip(dot)net>
Cc: "Erik Jones" <erik(at)myemma(dot)com>, "Jeff" <threshar(at)threshar(dot)is-a-geek(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Richard Huxton" <dev(at)archonet(dot)com>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: 7 hrs for a pg_restore?
Date: 2008-02-20 14:14:13
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
"Douglas J Hunley" <doug(at)hunley(dot)homeip(dot)net> writes:

> On Tuesday 19 February 2008 16:32:02 Erik Jones wrote:
>> pg_restore is a postgres client app that uses libpq to connect and,  
>> thus, will pick up anything in your $PGOPTIONS env variable.  So,
>> PGOPTONS="-c maintenance_work_mem=512MB" && pg_restore ....
> now that's just plain cool
> /me updates our wiki

I would suggest leaving out the && which only obfuscate what's going on here.

PGOPTIONS=... pg_restore ...

would work just as well and be clearer about what's going on.

  Gregory Stark
  Ask me about EnterpriseDB's Slony Replication support!

In response to


pgsql-performance by date

Next:From: Michael StoneDate: 2008-02-20 15:31:13
Subject: Re: Anyone using a SAN?
Previous:From: C. BergströmDate: 2008-02-20 13:52:42
Subject: Re: Anyone using a SAN?

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