Re: update faster way

From: Igor Korot <ikorot01(at)gmail(dot)com>
To: yudhi s <learnerdatabase99(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: update faster way
Date: 2024-09-14 03:29:12
Message-ID: CA+FnnTxqBu+eM1G-8LQhGXEqSdndUYPEk6rc4zSspCivRf9CZQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hii,

On Fri, Sep 13, 2024 at 10:22 PM yudhi s <learnerdatabase99(at)gmail(dot)com> wrote:
>
> Hello,
> We have to update a column value(from numbers like '123' to codes like 'abc' by looking into a reference table data) in a partitioned table with billions of rows in it, with each partition having 100's millions rows. As we tested for ~30million rows it's taking ~20minutes to update. So if we go by this calculation, it's going to take days for updating all the values. So my question is
>
> 1) If there is any inbuilt way of running the update query in parallel (e.g. using parallel hints etc) to make it run faster?
> 2) should we run each individual partition in a separate session (e.g. five partitions will have the updates done at same time from 5 different sessions)? And will it have any locking effect or we can just start the sessions and let them run without impacting our live transactions?

Do you have any indexes?
If not - you should, if yes - what are they?

Thank you.

>
> UPDATE tab_part1
> SET column1 = reftab.code
> FROM reference_tab reftab
> WHERE tab_part1.column1 = subquery.column1;
>
> Regards
> Yudhi

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message yudhi s 2024-09-14 03:58:52 Re: update faster way
Previous Message yudhi s 2024-09-14 03:13:34 update faster way