From: | Bricklen Anderson <BAnderson(at)PresiNET(dot)com> |
---|---|
To: | meetesh(dot)karia(at)alumni(dot)duke(dot)edu |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: ETL optimization |
Date: | 2005-06-23 20:16:50 |
Message-ID: | 42BB18B2.4040009@PresiNET.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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.
_______________________________
From | Date | Subject | |
---|---|---|---|
Next Message | Jacques Caron | 2005-06-23 21:56:27 | Re: ETL optimization |
Previous Message | Meetesh Karia | 2005-06-23 19:54:06 | Re: ETL optimization |