Re: 7 hrs for a pg_restore?
Greg Stark <stark@enterprisedb.com>
From: Gregory Stark <stark@enterprisedb.com>
To: "Douglas J Hunley" <doug@hunley.homeip.net>
Cc: "Erik Jones" <erik@myemma.com>, "Jeff" <threshar@threshar.is-a-geek.com>, "Tom Lane" <tgl@sss.pgh.pa.us>, "Richard Huxton" <dev@archonet.com>, <pgsql-performance@postgresql.org>
Date: 2008-02-20T14:14:13Z
Lists: pgsql-performance
"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!