Re: Hot Issue - Mailing list pgsql-performance

From Tom Lane
Subject Re: Hot Issue
Date
Msg-id 12784.1215016531@sss.pgh.pa.us
Whole thread Raw
In response to Re: Hot Issue  ("Gauri Kanekar" <meetgaurikanekar@gmail.com>)
List pgsql-performance
"Gauri Kanekar" <meetgaurikanekar@gmail.com> writes:
> Better HOT performance means.... 1st stat showed most of the updated tuples
> getting hot.
> But the 2nd stat showed that most of the updated tuples are NOT getting hot.

Well, as was noted upthread, you'd want to reduce the table fillfactor
(not index fillfactor) below 100 to improve the odds of being able to
do HOT updates.  But I wonder whether your application behavior changed.
Are you updating the rows in a way that'd make them wider?

            regards, tom lane

pgsql-performance by date:

Previous
From: "Gauri Kanekar"
Date:
Subject: Re: Hot Issue
Next
From: "Leví Teodoro da Silva"
Date:
Subject: [QUESTION]Concurrent Access