Re: Operator class parameters and sgml docs
Alexander Korotkov <a.korotkov@postgrespro.ru>
From: Alexander Korotkov <a.korotkov@postgrespro.ru>
To: Peter Geoghegan <pg@bowt.ie>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2020-05-21T00:17:31Z
Lists: pgsql-hackers
Hi, Peter! On Thu, May 21, 2020 at 12:37 AM Peter Geoghegan <pg@bowt.ie> wrote: > Commit 911e7020770 added a variety of new support routines to index > AMs. For example, it added a support function 5 to btree (see > BTOPTIONS_PROC), but didn't document this alongside the other support > functions in btree.sgml. > > It looks like the new support functions are fundamentally different to > the existing ones in that they exist only as a way of supplying > parameters to other support functions. The idea was to preserve > compatibility with the old support function signatures. Even still, I > think that the new support functions should get some mention alongside > the older support functions. > > I also wonder whether or not xindex.sgml needs to be updated to > account for opclass parameters. Thank you for pointing. I'm going to take a look on this in next few days. ------ Alexander Korotkov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
Commits
-
Language fixes for docs related to opclass options
- 70004a2a0c52 13.0 landed
- 14903f238ec9 14.0 landed
-
Minor corrections to docs related to opclass options
- b56d91ebd2be 13.0 landed
- 3be015c9fc02 14.0 landed
-
Add documentation for opclass options
- e6c6f427e356 13.0 landed
- 15cb2bd27009 14.0 landed
-
Implement operator class parameters
- 911e70207703 13.0 cited