| From: | Philippe Doussot <philippe(dot)doussot(at)up(dot)coop> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | rob stone <floriparob(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: update non-indexed value is slow if some non-related index/fk are enabled |
| Date: | 2021-09-07 11:59:19 |
| Message-ID: | 3205dd81-1735-8a14-296e-06c6c883cc50@up.coop |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 06/09/2021 16:13, David G. Johnston wrote:
> On Monday, September 6, 2021, Philippe Doussot <philippe(dot)doussot(at)up(dot)coop <mailto:philippe(dot)doussot(at)up(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-09-07 13:48:52 | Re: How to log bind values for statements that produce errors |
| Previous Message | Magnus Hagander | 2021-09-07 10:28:09 | Re: Choosing an index on partitioned tables. |