diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2018-07-19 13:48:05 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2018-07-19 14:53:50 -0400 |
commit | 0f49a2de96e7b58e15899b2639e096b771e45886 (patch) | |
tree | 354ba81e5f6588022a001ac7e4896c25adba48c7 /src/backend/access/transam/xlog.c | |
parent | 96bd49437cca5d7a6e4024c602a9fdbdbf7c7433 (diff) | |
download | postgresql-0f49a2de96e7b58e15899b2639e096b771e45886.tar.gz postgresql-0f49a2de96e7b58e15899b2639e096b771e45886.zip |
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
Diffstat (limited to 'src/backend/access/transam/xlog.c')
0 files changed, 0 insertions, 0 deletions