Search Postgresql Archives

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

Subject: Re: update non-indexed value is slow if some non-related index/fk are enabled
From: "David G. Johnston" <david.g.johnston@xxxxxxxxx>
Date: Mon, 6 Sep 2021 07:13:07 -0700
Cc: rob stone <floriparob@xxxxxxxxx>, Tom Lane <tgl@xxxxxxxxxxxxx>, "pgsql-general@xxxxxxxxxxxxxxxxxxxx" <pgsql-general@xxxxxxxxxxxxxxxxxxxx>
In-reply-to: <a0615923-0430-a31c-bef2-65580c30085e@up.coop>
References: <f5710d56-504f-46d9-986a-8ca03980363c@up.coop> <CAKFQuwZbx8v9Ect=FDk34FhJdCDw3ekQ=vDcKW==XaNTCiF5Cg@mail.gmail.com> <2875218.1630855266@sss.pgh.pa.us> <b67dcf853ff3ea29a60097737811e0186288362b.camel@gmail.com> <a0615923-0430-a31c-bef2-65580c30085e@up.coop>

On Monday, September 6, 2021, Philippe Doussot <philippe.doussot@xxxxxxx> 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.

Follow-Ups:
- Re: update non-indexed value is slow if some non-related index/fk are enabled
  - From: Peter J. Holzer
- Re: update non-indexed value is slow if some non-related index/fk are enabled
  - From: Philippe Doussot

References:
- update non-indexed value is slow if some non-related index/fk are enabled
  - From: Philippe Doussot
- Re: update non-indexed value is slow if some non-related index/fk are enabled
  - From: David G. Johnston
- Re: update non-indexed value is slow if some non-related index/fk are enabled
  - From: Tom Lane
- Re: update non-indexed value is slow if some non-related index/fk are enabled
  - From: rob stone
- Re: update non-indexed value is slow if some non-related index/fk are enabled
  - From: Philippe Doussot