MIME-Version: 1.0
In-Reply-To: <8CDAFB3EE5DFE5F-1AE0-21557@web-mmc-d02.sysops.aol.com>
References: <loom.20110310T163020-437@post.gmane.org>
	<AANLkTiks9aTwVyN-JW1Ep2cVoJabBF_fZfkk_43GRcNv@mail.gmail.com>
	<loom.20110311T195504-383@post.gmane.org>
	<AANLkTi=dGuvB_EuU43CbFUeuaG57-WXvypw+A1WKHhZ8@mail.gmail.com>
	<8CDAFB3EE5DFE5F-1AE0-21557@web-mmc-d02.sysops.aol.com>
From: Marti Raudsepp <marti@juffo.org>
Date: Mon, 14 Mar 2011 12:17:34 +0200
Message-ID: <AANLkTimVFRO3FFGo3YXf3tSTVNdXRmLh8STnmJt9eTRr@mail.gmail.com>
Subject: Re: Tuning massive UPDATES and GROUP BY's?
To: runner <runner@winning.com>
Cc: pgsql-performance@postgresql.org
Content-Type: text/plain; charset=UTF-8

On Sun, Mar 13, 2011 at 18:36, runner <runner@winning.com> wrote:
> Tried removing the indexes and other constraints just for
> the import but for a noob like me, this was too much to ask.  Maybe
> when I get more experience.

pgAdmin should make it pretty easy. Choose each index and constraint,
save the code from the "SQL pane" for when you need to restore it, and
do a right click -> Drop

> Other than being very inefficient, and consuming
> more time than necessary, is there any other down side to importing
> into an indexed table?

Doing so will result in somewhat larger (more bloated) indexes, but
generally the performance impact of this is minimal.

Regards,
Marti