On Tue, Oct 31, 2017 at 10:50:39AM +, steven.winfi...@cantabcapital.com
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/10/static/textsearch-indexes.html
> Description:
>
> https://www.postgresql.org/docs/current/static/textsearch-indexes.html
>
> The last paragraph mentions the dblink module, but surely postgres_fdw
> deserves a mention here too - especially with its increasing ability to push
> more of the query onto the foreign servers.
>
> Also, I think it would be worth mentioning elsewhere in the documentation
> (e.g. https://www.postgresql.org/docs/10/static/indexes-types.html) the
> impact that maintenance_work_mem has on the creation time for different
> index types - currently I can't find this anywhere else except on this FTS
> page.
I have applied the attached doc patch which will appear in PG 11.
Thanks.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
diff --git a/doc/src/sgml/textsearch.sgml b/doc/src/sgml/textsearch.sgml
new file mode 100644
index 4dc52ec..1a2f040
*** a/doc/src/sgml/textsearch.sgml
--- b/doc/src/sgml/textsearch.sgml
*** SELECT plainto_tsquery('supernovae stars
*** 3614,3621
allows the implementation of very fast searches with online update.
Partitioning can be done at the database level using table inheritance,
or by distributing documents over
!servers and collecting search results using the
!module. The latter is possible because ranking functions use
only local information.
--- 3614,3622
allows the implementation of very fast searches with online update.
Partitioning can be done at the database level using table inheritance,
or by distributing documents over
!servers and collecting external search results, e.g. via Foreign Data access.
!The latter is possible because ranking functions use
only local information.
