From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Joey Quinn <bjquinniii(at)gmail(dot)com> |
Cc: | Rémi Cura <remi(dot)cura(at)gmail(dot)com>, "Raymond O'Donnell" <rod(at)iol(dot)ie>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: tracking scripts... |
Date: | 2013-11-27 14:50:06 |
Message-ID: | CAHyXU0x-61QTP9C7M=MZdVsdEh7HZMiyZY1h0jQtrsKsom6abw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Nov 27, 2013 at 8:35 AM, Joey Quinn <bjquinniii(at)gmail(dot)com> wrote:
> So, no cancel... keeping my fingers crossed (rolling up on 170,000,000 ms -
> a bit over 47 hours - data folder size now at 1.11 TB).
>
> Fortunately, I'm pretty sure this will be my largest batch update (since the
> info is static, and available all at once, I was able to generate the
> complete script. In most cases, I will be retrieving data and that takes a
> bit longer).
>
> When I end up having to rebuild the entire thing on a separate system, can I
> divide the script up and launch it piecemeal in differ PGAdmin query windows
> for the parallel action? Or is there a particular command I have to give it?
For very large updates on mostly static data it may be better to
SELECT the data into a new table then swap it in when done. MY rule
of thumb is that updates are 10x more expensive than inserts,
particularly in terms of large operations.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Joey Quinn | 2013-11-27 15:00:48 | Re: tracking scripts... |
Previous Message | Janek Sendrowski | 2013-11-27 14:45:48 | Documentation of C functions |