From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Fix pg_get_indexdef()'s behavior for included index columns. |
Date: | 2018-07-19 18:54:12 |
Message-ID: | E1fgE44-0005ar-QR@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Fix pg_get_indexdef()'s behavior for included index columns.
The multi-argument form of pg_get_indexdef() failed to print anything when
asked to print a single index column that is an included column rather than
a key column. This seems an unintentional result of someone having tried
to take a short-cut and use the attrsOnly flag for two different purposes.
To fix, split said flag into two flags, attrsOnly which suppresses
non-attribute info, and keysOnly which suppresses included columns.
Add a test case using psql's \d command, which relies on that function.
(It's mighty tempting at this point to replace pg_get_indexdef_worker's
mess of boolean flag arguments with a single bitmask-of-flags argument,
which would allow making the call sites much more self-documenting.
But I refrained for the moment.)
Discussion: https://postgr.es/m/21724.1531943735@sss.pgh.pa.us
Branch
------
REL_11_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/0f49a2de96e7b58e15899b2639e096b771e45886
Modified Files
--------------
src/backend/utils/adt/ruleutils.c | 45 ++++++++++++++++-----------
src/test/regress/expected/index_including.out | 10 ++++++
src/test/regress/sql/index_including.sql | 1 +
3 files changed, 38 insertions(+), 18 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-07-19 19:42:01 | pgsql: Remove undocumented restriction against duplicate partition key |
Previous Message | Alexander Korotkov | 2018-07-19 18:27:03 | pgsql: Fix handling of empty uncompressed posting list pages in GIN |