Re: update non-indexed value is slow if some non-related index/fk are enabled - Mailing list pgsql-general

From David G. Johnston
Subject Re: update non-indexed value is slow if some non-related index/fk are enabled
Date
Msg-id CAKFQuwZXBg4C6CH7nJWO-C2qvjtkJq=MgvHN8_SYWydX7SNkng@mail.gmail.com
Whole thread Raw
In response to Re: update non-indexed value is slow if some non-related index/fk are enabled  (Philippe Doussot <philippe.doussot@up.coop>)
Responses Re: update non-indexed value is slow if some non-related index/fk are enabled  (Philippe Doussot <philippe.doussot@up.coop>)
Re: update non-indexed value is slow if some non-related index/fk are enabled  ("Peter J. Holzer" <hjp-pgsql@hjp.at>)
List pgsql-general
On Monday, September 6, 2021, Philippe Doussot <philippe.doussot@up.coop> wrote:
I whas hopping the same optimisation as you: Write in place.



How exactly would you expect “update-in-place” to work given the nature of MVCC?

David J.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_upgrade - fe_sendauth: no password supplied
Next
From: "Daniel Westermann (DWE)"
Date:
Subject: Behavior change in PostgreSQL 14Beta3 or bug?