> For the complete documentation index, see [llms.txt](https://docs.postgresql.tw/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.postgresql.tw/15/internals/database-physical-storage/storage-hot.md).

# 73.7. Heap-Only Tuples (HOT)

## 73.7. Heap-Only Tuples (HOT)

To allow for high concurrency, PostgreSQL uses [multiversion concurrency control](/15/the-sql-language/concurrency-control/introduction.md) (MVCC) to store rows. However, MVCC has some downsides for update queries. Specifically, updates require new versions of rows to be added to tables. This can also require new index entries for each updated row, and removal of old versions of rows and their index entries can be expensive.

To help reduce the overhead of updates, PostgreSQL has an optimization called heap-only tuples (HOT). This optimization is possible when:

* The update does not modify any columns referenced by the table's indexes, including expression and partial indexes.
* There is sufficient free space on the page containing the old row for the updated row.

In such cases, heap-only tuples provide two optimizations:

* New index entries are not needed to represent updated rows.
* Old versions of updated rows can be completely removed during normal operation, including `SELECT`s, instead of requiring periodic vacuum operations. (This is possible because indexes do not reference their [page item identifiers](/15/internals/database-physical-storage/database-page-layout.md).)

In summary, heap-only tuple updates can only be created if columns used by indexes are not updated. You can increase the likelihood of sufficient page space for HOT updates by decreasing a table's [`fillfactor`](/15/reference/sql-commands/create-table.md#RELOPTION-FILLFACTOR). If you don't, HOT updates will still happen because new rows will naturally migrate to new pages and existing pages with sufficient free space for new row versions. The system view [pg\_stat\_all\_tables](/15/server-administration/monitoring-database-activity/the-statistics-collector.md#MONITORING-PG-STAT-ALL-TABLES-VIEW) allows monitoring of the occurrence of HOT and non-HOT updates.

***

原文：[PostgreSQL 15.19 Documentation](/15/internals/database-physical-storage/storage-hot.md)（英文原文，待翻譯）


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.postgresql.tw/15/internals/database-physical-storage/storage-hot.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.