From: | Christopher Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Bulk Insert and Index use |
Date: | 2004-08-11 02:24:31 |
Message-ID: | m34qna76ow.fsf@wolfe.cbbrowne.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
In an attempt to throw the authorities off his trail, tech(at)wildcash(dot)com (Rudi Starcevic) transmitted:
> A minute for your thoughts and/or suggestions would be great.
Could you give a more concrete example? E.g. - the DDL for the
table(s), most particularly.
At first guess, I think you're worrying about a nonissue. Each insert
will lead to a _modification_ of the various indices, which costs
_something_, but which is WAY less expensive than creating each index
from scratch.
But perhaps I'm misreading things; DDL for the intended tables and
indices would be real handy.
--
output = ("cbbrowne" "@" "cbbrowne.com")
http://www.ntlug.org/~cbbrowne/linux.html
Rules of the Evil Overlord #21. "I will hire a talented fashion
designer to create original uniforms for my Legions of Terror, as
opposed to some cheap knock-offs that make them look like Nazi
stormtroopers, Roman footsoldiers, or savage Mongol hordes. All were
eventually defeated and I want my troops to have a more positive
mind-set." <http://www.eviloverlord.com/>
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory S. Williamson | 2004-08-11 02:27:48 | Re: Bulk Insert and Index use |
Previous Message | Jason Coene | 2004-08-11 01:06:37 | Re: Hardware upgrade for a high-traffic database |