| From: | Erik Jones <erik(at)myemma(dot)com> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | "Douglas J Hunley" <doug(at)hunley(dot)homeip(dot)net>, "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 16:27:32 |
| Message-ID: | 0C5E3C24-530F-40AD-8CB4-B0477A368F6E@myemma.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Feb 20, 2008, at 8:14 AM, Gregory Stark wrote:
> "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.
Right, that's just an unnecessary habit of mine.
Erik Jones
DBA | Emma®
erik(at)myemma(dot)com
800.595.4401 or 615.292.5888
615.292.0777 (fax)
Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-02-20 16:54:06 | Re: 7 hrs for a pg_restore? |
| Previous Message | Michael Stone | 2008-02-20 15:35:39 | Re: Anyone using a SAN? |