From: Tom Lane <tgl@sss.pgh.pa.us>
To: Morris de Oryx <morrisdeoryx@gmail.com>
cc: pgsql-general <pgsql-general@postgresql.org>
Subject: Re: Is there a way to translate pg_amop.amopstrategy into a description?
In-reply-to: <CAKqncch0vyy07-M-M5NPn7sFbQqZCnWoJfY2zF5i3mkfkzdwdQ@mail.gmail.com>
References: <CAKqncch0vyy07-M-M5NPn7sFbQqZCnWoJfY2zF5i3mkfkzdwdQ@mail.gmail.com>
Comments: In-reply-to Morris de Oryx <morrisdeoryx@gmail.com>
	message dated "Thu, 22 Aug 2024 17:34:39 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2087379.1724366535.1@sss.pgh.pa.us>
Date: Thu, 22 Aug 2024 18:42:15 -0400
Message-ID: <2087380.1724366535@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/2087380.1724366535%40sss.pgh.pa.us>
Precedence: bulk

Morris de Oryx <morrisdeoryx@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