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-28 20:02:46 |
Message-ID: | CAPpHfdtSPrBht3xdmUzhN6zhghTegf-gC9ff+JiGF31Jg6BNLw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, May 21, 2020 at 3:17 AM Alexander Korotkov
<a(dot)korotkov(at)postgrespro(dot)ru> wrote:
>
> 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.
I'm sorry for the delay. I was very busy with various stuff. I'm
going to post docs patch next week.
------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2020-05-28 21:14:25 | Re: WIP: WAL prefetch (another approach) |
Previous Message | Mark Dilger | 2020-05-28 19:35:17 | Re: Delaying/avoiding BTreeTupleGetNAtts() call within _bt_compare() |