Re: Running update in chunks?

From: Tim Uckun <timuckun(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Richard Huxton <dev(at)archonet(dot)com>, Kevin Grittner <kgrittn(at)mail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Running update in chunks?
Date: 2013-01-27 00:55:05
Message-ID: CAGuHJrPojfKnROcvpRsHbY0OPYuDodEORYdYvyzPVE+TcmXMVg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>
> That would be one solution, but I think a better one would be to not
> store "make_id" in "imports" in the first place, but instead to always
> fetch it by joining "imports" to "models" at query time.
>

My problem here is that the incoming data is quite messy so the join
conditions become weird (lots of ORs and such). A multi pass approach
seems to work better.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jasen Betts 2013-01-27 03:00:20 Re: Can LC_TIME affect timestamp input?
Previous Message Adrian Klaver 2013-01-26 23:57:09 Re: Cast double precision to integer & check for overflow