[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pgsql-bugs
Subject:    Re: BUG #18166: 100 Gb 18000000 records table update
From:       Tom Lane <tgl () sss ! pgh ! pa ! us>
Date:       2023-10-21 1:22:40
Message-ID: 4020107.1697851360 () sss ! pgh ! pa ! us
[Download RAW message or body]

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


[prev in list] [next in list] [prev in thread] [next in thread]