On 2021-09-06 07:13:07 -0700, David G. Johnston wrote:
> On Monday, September 6, 2021, Philippe Doussot
> 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?
Some databases (e.g. Oracl
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?
David J.
On Monday, September 6, 2021, Philippe Doussot
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.
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 records. You just del
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 the
update because the boo
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 the
> > > update because the boolean colu
"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 records. You just deleted one physical
> record a
On Friday, September 3, 2021, Philippe Doussot
wrote:
>
> 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 i
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
