From: Ruslan Ganeev <ruslan.ganeev@list.ru>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re[2]: BUG #18166: 100 Gb 18000000 records table update
Date: Sat, 21 Oct 2023 13:34:23 +0300
Message-ID: <1697884463.759529479@f703.i.mail.ru> (raw)
In-Reply-To: <4020107.1697851360@sss.pgh.pa.us>
References: <18166-8d0f3718572475ef@postgresql.org>
<4020107.1697851360@sss.pgh.pa.us>
Thank you very much
--
Отправлено из Mail.ru для Android суббота, 21 октября 2023г., 04:22 +03:00 от Tom Lane tgl@sss.pgh.pa.us :
>PG Bug reporting form < noreply@postgresql.org> writes:
> We tried to make a script, which sets enddate = '2022-12-31' for all
> records, having the value in «DataVip» that is not maximal. For other
> records the script set s enddate = null
> The problem is that the script is running for 6 hours, the main percentage
> of time is taken by the rebuilding of indexes.
>
>This is not a bug. However ... a common workaround for bulk updates
>like that is to drop all the table's indexes and then recreate them
>afterwards. It's often quicker than doing row-by-row index updates.
>
>regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: ruslan.ganeev@list.ru, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: Re[2]: BUG #18166: 100 Gb 18000000 records table update
In-Reply-To: <1697884463.759529479@f703.i.mail.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox