Adjust psql \d query to avoid use of @> operator.

Tom Lane <tgl@sss.pgh.pa.us>

Commit: 471d55859c11b40059aef7dd82f82b3a0dc338b1
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date: 2017-10-22T20:45:16Z
Releases: 11.0
Adjust psql \d query to avoid use of @> operator.

It seems that the parray_gin extension has seen fit to introduce a
"text[] @> text[]" operator, which conflicts with the core
"anyarray @> anyarray" operator, causing ambiguous-operator failures
if the input arguments are coercible to text[] without being exactly
that type.  This strikes me as a bad idea, but it's out there and
people use it.  As of v10, that breaks psql's query that tries to
test "pg_statistic_ext.stxkind @> '{d}'", since stxkind is char[].
The best workaround seems to be to avoid use of that operator.
We can use a scalar-vs-array test "'d' = any(stxkind)" instead;
that's arguably more readable anyway.

Per report from Justin Pryzby.  Backpatch to v10 where this
query was added.

Discussion: https://postgr.es/m/20171022181525.GA21884@telsasoft.com

Files

PathChange+/−
src/bin/psql/describe.c modified +2 −2

Discussion