Thanks for the confirmation. And, I'd say that this feature would go under
"nice to have" rather than anything more important. Although, it *would *be
nice.

On Thu, Aug 22, 2024 at 5:42 PM Tom Lane <t...@sss.pgh.pa.us> wrote:

> Morris de Oryx <morrisdeo...@gmail.com> writes:
> > What I'm hoping for is a function like
> > get_opt_class_strategy_description(optclass, straregy_number)  I've
> > looked at the source a bit, and it seems that there is no such
> > function, and that it might well be difficult to implement. The
> > strategy numbers are, as far as I can see, local to the specific
> > opt_class, which has no requirement to label them in any particular
> > way.
>
> That's correct.  For btree and hash, the meanings of the strategy
> numbers are determined by the index AM; but for (IIRC) all of our
> other index AMs they're determined by the individual opclass.  So
> anything like this would have to be implemented by dedicated code
> in each opclass.  Perhaps that's worth doing, but it'd be a fair
> amount of work.
>
>                         regards, tom lane
>

Reply via email to