From: Gregory Stark <stark@enterprisedb.com>
To: Douglas J Hunley <doug@hunley.homeip.net>
Cc: Erik Jones <erik@myemma.com>
Cc: Jeff <threshar@threshar.is-a-geek.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Richard Huxton <dev@archonet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: 7 hrs for a pg_restore?
Date: Wed, 20 Feb 2008 14:14:13 +0000
Message-ID: <874pc3ww96.fsf@oxford.xeocode.com> (raw)
In-Reply-To: <200802200826.38611.doug@hunley.homeip.net>
References: <200802191303.58840.doug@hunley.homeip.net>
<200802191555.43340.doug@hunley.homeip.net>
<080DA59E-2C02-4370-8584-FA7C8CC008B0@myemma.com>
<200802200826.38611.doug@hunley.homeip.net>
"Douglas J Hunley" <doug@hunley.homeip.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
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
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: stark@enterprisedb.com, doug@hunley.homeip.net, erik@myemma.com, threshar@threshar.is-a-geek.com, tgl@sss.pgh.pa.us, dev@archonet.com
Subject: Re: 7 hrs for a pg_restore?
In-Reply-To: <874pc3ww96.fsf@oxford.xeocode.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