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

From Philippe Doussot
Subject Re: update non-indexed value is slow if some non-related index/fk are enabled
Date
Msg-id 3205dd81-1735-8a14-296e-06c6c883cc50@up.coop
Whole thread Raw
In response to Re: update non-indexed value is slow if some non-related index/fk are enabled  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general

On 06/09/2021 16:13, David G. Johnston wrote:
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.

Yes right, it is probably not possible due to concurrency.

I don't know enough about it.

My expectations was naive


Again, thanks David for pointing me to the fact that the raw record was new on each update.


Philippe

pgsql-general by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Choosing an index on partitioned tables.
Next
From: Tom Lane
Date:
Subject: Re: How to log bind values for statements that produce errors