From 7322f2afedcc2f427e997d1535a503613a83f088 Mon Sep 17 00:00:00 2001 From: Ivan Kohler Date: Sat, 24 Sep 2016 10:28:06 -0700 Subject: rt 4.2.13 ticket#13852 --- rt/docs/UPGRADING-4.2 | 10 ++++++++-- rt/docs/full_text_indexing.pod | 7 +++++++ 2 files changed, 15 insertions(+), 2 deletions(-) (limited to 'rt/docs') diff --git a/rt/docs/UPGRADING-4.2 b/rt/docs/UPGRADING-4.2 index 76aa96d15..45a000e87 100644 --- a/rt/docs/UPGRADING-4.2 +++ b/rt/docs/UPGRADING-4.2 @@ -327,11 +327,17 @@ functionality can now be implemented via C<%DatabaseExtraDSN>. C<$DatabaseRequireSSL> has been removed, and setting it will trigger an informational message that setting it is ineffective. -The full-text indexing defaults for PostgreSQL have changed; GiST is now +The full-text indexing defaults for PostgreSQL have changed; GIN is now the suggested index, as well as storing data in a separate AttachmentsIndex table. Both changes improve lookup speed. For improved search performance, you may wish to drop existing C -and C indexes on C, and re-generate the index using +and C indexes on C, and re-generate the index using C. +=head1 UPGRADING FROM 4.2.12 AND EARLIER + +New deployments install an C that includes a C +to allow Unicode to be used in config. You may wish to add a C to +the top of your C if you haven't already done so. + =cut diff --git a/rt/docs/full_text_indexing.pod b/rt/docs/full_text_indexing.pod index 24169cb14..189c346cf 100644 --- a/rt/docs/full_text_indexing.pod +++ b/rt/docs/full_text_indexing.pod @@ -273,4 +273,11 @@ option to 1, while leaving C set to 0: This is not generally suggested, as unindexed full-text searching can cause severe performance problems. +=head1 LIMIT ATTACHMENT SIZE + +On some systems, very large attachments can cause memory and other +performance issues for the indexer making it unable to complete +indexing. See L for +details on setting a maximum attachment size to index. + =cut -- cgit v1.2.1