Message-ID: <42BB18B2.4040009@PresiNET.com>
Date: Thu, 23 Jun 2005 13:16:50 -0700
From: Bricklen Anderson <BAnderson@PresiNET.com>
User-Agent: Debian Thunderbird 1.0.2 (X11/20050602)
MIME-Version: 1.0
To: meetesh.karia@alumni.duke.edu
Cc: pgsql-performance@postgresql.org
Subject: Re: ETL optimization
References: <42BB0F9C.2050207@PresiNET.com>
	<fc5b04ca05062312546323c07e@mail.gmail.com>
In-Reply-To: <fc5b04ca05062312546323c07e@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Meetesh Karia wrote:
> I don't know what this will change wrt how often you need to run VACUUM
> (I'm a SQL Server guy), but instead of an update and insert, try a
> delete and insert.  You'll only have to find the duplicate rows once and
> your insert doesn't need a where clause.
> 
> Meetesh
> 
Vacuum analyze in generally run about once an hour. You know, I didn't even
think to try a delete + insert combo (which will not be visible to the other
queries that are occurring). Truncate is out of the question, because of the
aforementioned queries, but I'll give the d+i a shot.

Thanks!


-- 
_______________________________

This e-mail may be privileged and/or confidential, and the sender does
not waive any related rights and obligations. Any distribution, use or
copying of this e-mail or the information it contains by other than an
intended recipient is unauthorized. If you received this e-mail in
error, please advise me (by return e-mail or otherwise) immediately.
_______________________________