On Thu, Jul 28, 2016 at 10:53:47AM -0400, Robert Haas wrote:
> [1] I look forward to a future PostgreSQL conference in which the
> struggle to pronounce "HMT" forms a recurring theme.
For maximal confusion, this should really be called a Heap Often
Tuple.
Best,
David.
--
David Fetter
Robert Haas wrote:
> If I understand correctly, we currently deem an update to be non-HOT
> whenever any indexed column is updated. This is because tuple
> versions created by HOT updates can later be removed by HOT pruning,
> which means that they must not be referenced by index entries.
>
On 28/07/16 16:53, Robert Haas wrote:
If I understand correctly, we currently deem an update to be non-HOT
whenever any indexed column is updated. This is because tuple
versions created by HOT updates can later be removed by HOT pruning,
which means that they must not be referenced by index
If I understand correctly, we currently deem an update to be non-HOT
whenever any indexed column is updated. This is because tuple
versions created by HOT updates can later be removed by HOT pruning,
which means that they must not be referenced by index entries.
Otherwise, after HOT pruning
