Search Postgresql Archives

Re: "Healing" a table after massive updates

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Sep 11, 2008 at 11:15 AM, Alan Hodgson <ahodgson@xxxxxxxxx> wrote:
> On Thursday 11 September 2008, "Gauthier, Dave" <dave.gauthier@xxxxxxxxx>
> wrote:
>> I have a job that loads a large table, but then has to "update" about
>> half the records for various reasons.  My perception of what happens on
>> update for a particular recors is...
>>
>> - a new record will be inserted with the updated value(s).
>>
>> - The old record is marked as being obselete.
>>
>
> What you might consider doing is loading the data into a temp table,
> updating it there, then copying that data into the final destination.
> Depending on the indexes involved, you might even find this to be faster.

Especially if you can drop then recreate them on the real table before
reimporting them to it.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux