pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Paquier <michael@paquier.xyz>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: pageinspect: Fix gist_page_items() with included columns
Date: Fri, 19 May 2023 03:39:45 +0000
Message-ID: <E1pzqy1-000c5B-TV@gemulon.postgresql.org> (raw)

pageinspect: Fix gist_page_items() with included columns

Non-leaf pages of GiST indexes contain key attributes, leaf pages
contain both key and non-key attributes, and gist_page_items() ignored
the handling of non-key attributes.  This caused a few problems when
using gist_page_items() on a GiST index with INCLUDE:
- On a non-leaf page, the function would crash.
- On a leaf page, the function would work, but miss to display all the
values for included attributes.

This commit fixes gist_page_items() to handle such cases in a more
appropriate way, and now displays the values of key and non-key
attributes for each item separately in a style consistent with what
ruleutils.c would generate for the attribute list, depending on the page
type dealt with.  In a way similar to how a record is displayed, values
would be double-quoted for key or non-key attributes if required.

ruleutils.c did not provide a routine able to control if non-key
attributes should be displayed, so an extended() routine for index
definitions is added to work around the leaf and non-leaf page
differences.

While on it, this commit fixes a third problem related to the amount of
data reported for key attributes.  The code originally relied on
BuildIndexValueDescription() (used for error reports on constraints)
that would not print all the data stored in the index but the index
opclass's input type, so this limited the amount of information
available.  This switch makes gist_page_items() much cheaper as there is
no need to run ACL checks for each item printed, which is not an issue
anyway as superuser rights are required to execute the functions of
pageinspect.  Opclasses whose data cannot be displayed can rely on
gist_page_items_bytea().

The documentation of this function was slightly incorrect for the
output results generated on HEAD and v15, so adjust it on these
branches.

Author: Alexander Lakhin, Michael Paquier
Discussion: https://postgr.es/m/17884-cb8c326522977acb@postgresql.org
Backpatch-through: 14

Branch
------
REL_15_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/2dd77822178807f3da988e1d873777685d9f7504

Modified Files
--------------
contrib/pageinspect/expected/gist.out |  53 +++++++++++++-----
contrib/pageinspect/gistfuncs.c       | 102 ++++++++++++++++++++++++++++++++--
contrib/pageinspect/sql/gist.sql      |  14 +++++
doc/src/sgml/pageinspect.sgml         |  19 +++----
src/backend/utils/adt/ruleutils.c     |  16 ++++++
src/include/utils/ruleutils.h         |   5 ++
6 files changed, 178 insertions(+), 31 deletions(-)



view thread (3+ messages)  latest in thread

Message-ID: <E1pzqy1-000c5B-TV@gemulon.postgresql.org>
Permalink:  ../E1pzqy1-000c5B-TV@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1pzqy1-000c5B-TV@gemulon.postgresql.org

 · 

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: pgsql-committers@postgresql.org
  Cc: michael@paquier.xyz, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: pageinspect: Fix gist_page_items() with included columns
  In-Reply-To: <E1pzqy1-000c5B-TV@gemulon.postgresql.org>

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

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