uhlnOa6Vsx6-MT2IBatnqI7vmjUul2-_EjYgUpYaHQ5q1LqjIR9-pxUHfikOYW7y2eM8WGWMEw6PlnMfKnTaOZP-y2iUHa7jlBrUK_DYDxjdcFR32CefiLPg-hrxT5OaW-c3bv9zu5BEdrLA==>
Philippe DOUSSOT
ARCHITECTE TECHNIQUE
DIRECTION DES SOLUTIONS ARCHE MC2 DOMICILE
philippe.doussot@arche‑mc2.fr
Hi,
Just want to say THANK YOU all (Robert Haas, Vik Fearing, ..) for these feature
I just discover available since 9.6 !
although I am still in version 9.5
Philippe
On 06/09/2021 16:13, David G. Johnston wrote:
On Monday, September 6, 2021, Philippe Doussot mailto:philippe.dous...@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?
D
On 05/09/2021 17:21, Tom Lane wrote:
"David G. Johnston" writes:
On Friday, September 3, 2021, Philippe Doussot
wrote:
I don't understand why disabling all index from the table speed up the
update because the boolean column is not indexed
Index entries point to physical rec
On 06/09/2021 10:21, rob stone wrote:
On Sun, 2021-09-05 at 11:21 -0400, Tom Lane wrote:
"David G. Johnston" writes:
On Friday, September 3, 2021, Philippe Doussot <
philippe.dous...@up.coop>
wrote:
I don't understand why disabling all index from the table speed
up t
Hi all,
I'm look for some hint about this behaviour :
One UPDATE of one boolean value which is non-indexed take some time ( for many
tuples .. 3 Millions ).
But if we disable all indexes/fk the UPDATE is 10x faster and do 10x less
shared hit .
I don't understand why disabling all index from
