Re: Operator class parameters and sgml docs
Peter Geoghegan <pg@bowt.ie>
From: Peter Geoghegan <pg@bowt.ie>
To: Alexander Korotkov <a.korotkov@postgrespro.ru>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2020-06-16T23:50:37Z
Lists: pgsql-hackers
On Tue, Jun 16, 2020 at 4:24 AM Alexander Korotkov <a.korotkov@postgrespro.ru> wrote: > Thank you for patience. The documentation patch is attached. I think > it requires review by native english speaker. * "...paramaters that controls" should be "...paramaters that control". * "with set of operator class specific option" should be "with a set of operator class specific options". * "The options could be accessible from each support function" should be "The options can be accessed from other support functions" (At least I think that that's what you meant) It's very hard to write documentation like this, even for native English speakers. I think that it's important to have something in place, though. The GiST example helps a lot. -- Peter Geoghegan
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