Re: No longer possible to query catalogs for index capabilities? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: No longer possible to query catalogs for index capabilities?
Date
Msg-id 23668.1469454897@sss.pgh.pa.us
Whole thread Raw
In response to No longer possible to query catalogs for index capabilities?  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Responses Re: No longer possible to query catalogs for index capabilities?
List pgsql-hackers
Andrew Gierth <andrew@tao11.riddles.org.uk> writes:
> With the gutting of pg_am in 9.6, there seems to be no longer any way
> for a query of the system catalogs to discover any of the index
> capabilities that were formerly columns in pg_am (notably amcanorder,
> amcanorderbyop, amclusterable, amsearcharray, amsearchnulls).

> Am I missing something or is this a significant oversight?

It's absolutely not an oversight.  We asked when 65c5fcd35 went in
whether there was still any need for that information to be available at
the SQL level, and nobody appeared to care.  We could in theory expose
a view to show the data --- but since a large part of the point of that
change was to not need initdb for AM API changes, and to not be
constrained to exactly SQL-compatible representations within that API,
I'm disinclined to do so without a fairly compelling argument why it's
needed.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: No longer possible to query catalogs for index capabilities?
Next
From: Andrew Gierth
Date:
Subject: Re: No longer possible to query catalogs for index capabilities?