Re: Running update in chunks?

From: "Kevin Grittner" <kgrittn(at)mail(dot)com>
To: "Tim Uckun" <timuckun(at)gmail(dot)com>,"Richard Huxton" <dev(at)archonet(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Running update in chunks?
Date: 2013-01-21 22:05:23
Message-ID: 20130121220523.120610@gmx.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tim Uckun wrote:

> If you have any suggestions I am all ears. For the purposes of this
> discussion we can narrow down the problem this update statement.
>
> Update imports set make_id = null.

Well, that simplifies things.

First off, what does it say for rows affected? (Hint, if you really
are using a default configuration and it doesn't say 0 rows
affected, please show us the actual query used.)

Second, try connecting to the database as a superuser and running:

VACUUM ANALYZE imports;
-- (show us the results)
VACUUM FULL imports;
VACUUM FREEZE ANALYZE;  -- (don't specify a table)

Then try your query and see whether performance is any different.

-Kevin

Responses

Browse pgsql-general by date

  From Date Subject
Next Message patrick keshishian 2013-01-21 22:07:53 Re: Running update in chunks?
Previous Message Kevin Grittner 2013-01-21 21:50:22 Re: Running update in chunks?