summaryrefslogtreecommitdiffstats
path: root/doc/src/sgml/storage.sgml
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-05-14 19:16:20 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-05-14 19:16:20 +0000
commit323bcca5249c707b68d9f6d921d86fd750bcf33e (patch)
tree07b4722c510482f5ee2fdcc3d381fc77747b0178 /doc/src/sgml/storage.sgml
parentAdding debian version 16.2-2. (diff)
downloadpostgresql-16-323bcca5249c707b68d9f6d921d86fd750bcf33e.tar.xz
postgresql-16-323bcca5249c707b68d9f6d921d86fd750bcf33e.zip
Merging upstream version 16.3.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'doc/src/sgml/storage.sgml')
-rw-r--r--doc/src/sgml/storage.sgml21
1 files changed, 11 insertions, 10 deletions
diff --git a/doc/src/sgml/storage.sgml b/doc/src/sgml/storage.sgml
index 3ea4e55..aabb1d5 100644
--- a/doc/src/sgml/storage.sgml
+++ b/doc/src/sgml/storage.sgml
@@ -1097,8 +1097,10 @@ data. Empty in ordinary tables.</entry>
<itemizedlist>
<listitem>
<para>
- The update does not modify any columns referenced by the table's
- indexes, including expression and partial indexes.
+ The update does not modify any columns referenced by the table's indexes,
+ not including summarizing indexes. The only summarizing index method in
+ the core <productname>PostgreSQL</productname> distribution is <link
+ linkend="brin">BRIN</link>.
</para>
</listitem>
<listitem>
@@ -1114,7 +1116,8 @@ data. Empty in ordinary tables.</entry>
<itemizedlist>
<listitem>
<para>
- New index entries are not needed to represent updated rows.
+ New index entries are not needed to represent updated rows, however,
+ summary indexes may still need to be updated.
</para>
</listitem>
<listitem>
@@ -1130,14 +1133,12 @@ data. Empty in ordinary tables.</entry>
</para>
<para>
- 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
+ You can increase the likelihood of sufficient page space for
<acronym>HOT</acronym> updates by decreasing a table's <link
- linkend="reloption-fillfactor"><literal>fillfactor</literal></link>.
- If you don't, <acronym>HOT</acronym> 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 <link
+ linkend="reloption-fillfactor"><literal>fillfactor</literal></link>. If you
+ don't, <acronym>HOT</acronym> 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 <link
linkend="monitoring-pg-stat-all-tables-view">pg_stat_all_tables</link>
allows monitoring of the occurrence of HOT and non-HOT updates.
</para>