Re: HOT update: why must ALL indexes should be update?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Daniel Wu <staywithpin(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: HOT update: why must ALL indexes should be update?
Date: 2023-04-21 14:19:42
Message-ID: 3338045.1682086782@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Daniel Wu <staywithpin(at)gmail(dot)com> writes:
> We have many indexes on a table. The chance is that any column could be
> some part of an index. I understand that when an index has a column that is
> updated, we can't use HOT, because the index entry could point to a totally
> different row. But if I have 10 indexes, if only 1 index will be updated,
> why the rest 9 indexes couldn't use HOT update?

Whether it's a HOT update is a property of the table row, not of
individual indexes.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2023-04-21 14:43:34 Re: Why does the planner reduce the planned rows when filtering single values in an array
Previous Message Daniel Wu 2023-04-21 14:06:41 HOT update: why must ALL indexes should be update?