public inbox for [email protected]  

help / color / mirror / Atom feed

From: Elizabeth Christensen <[email protected]>
To: Stephen Frost <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH] updates to docs about HOT updates for BRIN
Date: Mon, 26 Feb 2024 16:25:39 -0600
Message-ID: <[email protected]> (raw)
In-Reply-To: <Zd0O8CqQM1ms/[email protected]>
References: <CABoUFXRjisr58Ct_3VsFEdQx+fJeQTWTdJnM7XAp=8MUbtoa9A@mail.gmail.com>
	<Zd0O8CqQM1ms/[email protected]>



> On Feb 26, 2024, at 4:21 PM, Stephen Frost <[email protected]> wrote:
> 
> Greetings,
> 
> * Elizabeth Christensen ([email protected]) wrote:
>> I have a small documentation patch to the HOT updates page
>> <https://www.postgresql.org/docs/current/storage-hot.html>to add references
>> to summary (BRIN) indexes not blocking HOT updates
>> <https://www.postgresql.org/message-id/[email protected]...;,
>> committed 19d8e2308b.
> 
> Sounds good to me, though the attached patch didn't want to apply, and
> it isn't immediately clear to me why, but perhaps you could try saving
> the patch from a different editor and re-sending it?
> 
> Thanks,
> 
> Stephen

Thanks Stephen, attempt #2 here. 

Elizabeth



Attachments:

  [application/octet-stream] v2-0001-Adding-Summary-Index-Info-to-HOT-Update-Documentatio.patch (2.5K, ../[email protected]/2-v2-0001-Adding-Summary-Index-Info-to-HOT-Update-Documentatio.patch)
  download | inline diff:
From: elizabeth-christensen <[email protected]>
Date: Mon, 26 Feb 2024 12:09:22 -0600
Subject: [PATCH] Adding Summary Index Info to HOT Update Documentation page

Commit 19d8e2308b changed when the HOT update optimization is possible but neglected to update the Heap-Only Tuples (HOT) documentation.  This patch updates that documentation accordingly.

Author: Elizabeth Christensen
Backpatch-through: 16
Discussion: 
---
 doc/src/sgml/storage.sgml | 18 ++++++++++--------
 1 file changed, 10 insertions(+), 8 deletions(-)

diff --git a/doc/src/sgml/storage.sgml b/doc/src/sgml/storage.sgml
index 3ea4e5526d..314469706e 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 only modifies columns which are un-indexed or are only indexed with 
+     summarizing indexes (such as BRIN) and does not update any columns referenced 
+     by the table's non-summary indexes, including expression and partial 
+     non-summary indexes.
      </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,11 +1133,10 @@ 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
-  <acronym>HOT</acronym> updates by decreasing a table's <link
-  linkend="reloption-fillfactor"><literal>fillfactor</literal></link>.
+  In summary, heap-only tuple updates can only be created if columns used by 
+  non-summary indexes are not updated. 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
-- 
2.37.0

view thread (5+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: [PATCH] updates to docs about HOT updates for BRIN
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox