Horton

Re: Probable documentation errors or improvements

Justin Pryzby <pryzby@telsasoft.com>

View thread View on postgr.es
From: Justin Pryzby <pryzby@telsasoft.com>
To: Yaroslav <ladayaroslav@yandex.ru>
Cc: pgsql-hackers@postgresql.org
Date: 2020-09-19T17:55:59Z
Lists: pgsql-hackers 
On Thu, Sep 10, 2020 at 12:19:55PM -0700, Yaroslav wrote:
> Disclaimer: I'm not a native speaker, so not sure those are actually
> incorrect, and can't offer non-trivial suggestions.

https://www.postgresql.org/message-id/flat/CAKFQuwZh3k_CX2-%2BNcZ%3DFZss4bX6ASxDFEXJTY6u4wTH%2BG8%2BKA%40mail.gmail.com#9f9eba0cbbf9b57455503537575f5339

Most of these appear to be reasonable corrections or improvements.

Would you want to submit a patch against the master branch ?
It'll be easier for people to read when it's in a consistent format.
And less work to read it than to write it.

I suggest to first handle the 10+ changes which are most important and in need
of fixing.  After a couple rounds, then see if what's left is worth patching.

-- 
Justin

Commits

  1. doc: Remove more notes about compatibilities with past versions

  2. Misc documentation fixes.

  3. Fix TRUNCATE doc: ALTER SEQUENCE RESTART is now transactional.

  4. Fix output of tsquery example in docs.

  5. Fix doc for full text search distance operator.

  6. Phrase full text search.