Re[2]: BUG #18166: 100 Gb 18000000 records table update - Mailing list pgsql-bugs

From Ruslan Ganeev
Subject Re[2]: BUG #18166: 100 Gb 18000000 records table update
Date
Msg-id 1697884463.759529479@f703.i.mail.ru
Whole thread Raw
In response to Re: BUG #18166: 100 Gb 18000000 records table update  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs

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

pgsql-bugs by date:

Previous
From: Alexander Lakhin
Date:
Subject: Re: BUG #18165: Could not duplicate handle for "Global/PostgreSQL.xxxxxxxxxx": Bad file descriptor
Next
From: "Boyer, Maxime (he/him | il/lui)"
Date:
Subject: RE: BUG #18165: Could not duplicate handle for "Global/PostgreSQL.xxxxxxxxxx": Bad file descriptor