From: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Operator class parameters and sgml docs |
Date: | 2020-05-21 00:17:31 |
Message-ID: | CAPpHfdvG7GKdgBG2U3B-s10fFaneZ79c9MWTtYtMGwyjK51OYg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi, Peter!
On Thu, May 21, 2020 at 12:37 AM Peter Geoghegan <pg(at)bowt(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2020-05-21 00:32:55 | Re: Adding missing object access hook invocations |
Previous Message | Tomas Vondra | 2020-05-21 00:12:55 | Re: Trouble with hashagg spill I/O pattern and costing |