X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (mx1.hub.org [200.46.208.251])
	by postgresql.org (Postfix) with ESMTP id 7BB9E9FA5DD
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Fri, 26 May 2006 16:05:44 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024)
	with ESMTP id 99160-01-2
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Fri, 26 May 2006 16:05:36 -0300 (ADT)
X-Greylist: domain auto-whitelisted by SQLgrey-
Received: from nf-out-0910.google.com (nf-out-0910.google.com
 [64.233.182.189])
	by postgresql.org (Postfix) with ESMTP id BF9519FA12E
	for <pgsql-performance@postgresql.org>;
	Fri, 26 May 2006 16:05:33 -0300 (ADT)
Received: by nf-out-0910.google.com with SMTP id l36so113647nfa
	for <pgsql-performance@postgresql.org>;
	Fri, 26 May 2006 12:05:31 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
	b=AGU5ksD/lGvDhS8EMIMAgqE779vJf4Jt949UuODG8Nl/2XsboldotgVsQ3Rybgy0YmfT/MCADQahPb4WtAgXRG05HBnglFEnI4MohC027Du91BAu64n3ZorMEGKFLrlrPFPootwuLzxtncsoSr8E6SadEU4KhVck5LDxeS1RcgA=
Received: by 10.48.203.12 with SMTP id a12mr7406nfg;
	Fri, 26 May 2006 12:04:59 -0700 (PDT)
Received: by 10.48.164.19 with HTTP; Fri, 26 May 2006 12:04:59 -0700 (PDT)
Message-ID: <ce4072df0605261204o7f027120m70b16c2f796cce5b@mail.gmail.com>
Date: Fri, 26 May 2006 15:04:59 -0400
From: "Worky Workerson" <worky.workerson@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: Bulk loading/merging
In-Reply-To: <ce4072df0605261148g4ec22267gc54b6b445e47c855@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_217414_4407177.1148670299461"
References: <ce4072df0605261148g4ec22267gc54b6b445e47c855@mail.gmail.com>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200605/545
X-Sequence-Number: 19332

------=_Part_217414_4407177.1148670299461
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Another little question ... would using any sort of TEMP table help out, i.=
e.
loading the unaggregated data into a TEMP table, aggregating the data via a
SELECT INTO another TEMP table, and then finally INSERT ... SELECT into the
master, aggregated, triggered table?  It seems like this might be a win if
A) the TEMP tables fit into memory, and B) the load data aggregates well.
Worst case (i.e. all unique data in the load) seems like it might take much
longer, however, since I'm creating 2 new TEMP tables ....

------=_Part_217414_4407177.1148670299461
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Another little question ... would using any sort of TEMP table help out, i.=
e. loading the unaggregated data into a TEMP table, aggregating the data vi=
a a SELECT INTO another TEMP table, and then finally INSERT ... SELECT into=
 the master, aggregated, triggered table?&nbsp; It seems like this might be=
 a win if A) the TEMP tables fit into memory, and B) the load data aggregat=
es well.&nbsp; Worst case (
i.e. all unique data in the load) seems like it might take much longer, how=
ever, since I'm creating 2 new TEMP tables ....<br><br>

------=_Part_217414_4407177.1148670299461--