Re: Tuning massive UPDATES and GROUP BY's? - Mailing list pgsql-performance

From Marti Raudsepp
Subject Re: Tuning massive UPDATES and GROUP BY's?
Date
Msg-id AANLkTimVFRO3FFGo3YXf3tSTVNdXRmLh8STnmJt9eTRr@mail.gmail.com
Whole thread Raw
In response to Re: Tuning massive UPDATES and GROUP BY's?  (runner <runner@winning.com>)
Responses Re: Tuning massive UPDATES and GROUP BY's?
List pgsql-performance
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

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Planner wrongly shuns multi-column index for select .. order by col1, col2 limit 1
Next
From: Greg Spiegelberg
Date:
Subject: Re: Tuning massive UPDATES and GROUP BY's?