From: "jay" <jackem.mojx@alibaba-inc.com>
To: "'Ryan Hansen'" <ryan.hansen@brightbuilders.com>,
	<pgsql-performance@postgresql.org>
References: <48C8006F.50706@brightbuilders.com>
Subject: =?gb2312?B?tPC4tDogW1BFUkZPUk1dIEltcHJvdmUgQ09QWSBwZXJmb3JtYW5jZQ==?=
	=?gb2312?B?IGZvciBsYXJnZSBkYXRhIHNldHM=?=
Date: Thu, 11 Sep 2008 09:23:04 +0800
Message-ID: <003a01c913ac$f0723910$6744000a@hz.ali.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AckTaLm1NuWt/L5mTkS8pKCfuoyNPQAQxXfg
In-Reply-To: <48C8006F.50706@brightbuilders.com>

I suspect your table has index, or checkpoint_segments is small and lead =
PG
do checkpoint frequently.=20
If the table has index or constraint, drop it and copy it ,after copy
finished, do create index or constraint again.
If checkpoint_segments is small, enlarge it.
And also you can turn fsync off when you do copy, after finish, turn it =
on
again.
And also you can enlarge maintenance_work_mem.

If you take above, time cost will down significantly.

	 =C4=AA=BD=A8=CF=E9=09
=B0=A2=C0=EF=B0=CD=B0=CD=C8=ED=BC=FE(=C9=CF=BA=A3)=D3=D0=CF=DE=B9=AB=CB=BE=

=D1=D0=B7=A2=D6=D0=D0=C4=A3=ADIM=B7=FE=CE=F1=B6=CB=BF=AA=B7=A2=B2=BF=20
=C1=AA=CF=B5=B7=BD=CA=BD:86-0571-85022088-13072
=C3=B3=D2=D7=CD=A8ID:jaymo =CC=D4=B1=A6ID:jackem
=B9=AB=CB=BE=CD=F8=D5=BE:www.alisoft.com
wiki:http://10.0.32.21:1688/confluence/pages/viewpage.action?pageId=3D103=
38

-----=D3=CA=BC=FE=D4=AD=BC=FE-----
=B7=A2=BC=FE=C8=CB: pgsql-performance-owner@postgresql.org
[mailto:pgsql-performance-owner@postgresql.org] =B4=FA=B1=ED Ryan Hansen
=B7=A2=CB=CD=CA=B1=BC=E4: 2008=C4=EA9=D4=C211=C8=D5 1:14
=CA=D5=BC=FE=C8=CB: pgsql-performance@postgresql.org
=D6=F7=CC=E2: Re: [PERFORM] Improve COPY performance for large data sets

NEVERMIND!!

I found it.  Turns out there was still a constraint on the table.  Once=20
I dropped that, the time went down to 44 minutes.

Maybe I am an idiot after all. :)

-Ryan