>>>>> "Tom" == Tom Lane <[email protected]> writes:
Tom> But we need to be clear in the documentation about what this
Tom> property actually means. My objection to having it answer at the
Tom> index or column level is basically that that encourages confusion
Tom> as to what it means.
OK. Here's new output with the scope changes, and some of the names
changed in an attempt to make them clearer:
cap | AM | Index | Column
--------------------+----+-------+--------
asc | | | t
desc | | | f
nulls_first | | | f
nulls_last | | | t
orderable | | | t
distance_orderable | | | f
returnable | | | t
search_array | | | t
search_nulls | | | t
clusterable | | t |
backward_scan | | t |
index_scan | | t |
bitmap_scan | | t |
can_order | t | |
can_unique | t | |
can_multi_col | t | |
can_exclude | t | |
(17 rows)
(The can_* names are reserved for the AM level where we're asking about
the abstract capabilities of the AM.)
Better? Worse? Any more improvements to the names?
--
Andrew (irc:RhodiumToad)
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
