From: Tom Lane <tgl@sss.pgh.pa.us>
To: obartunov@gmail.com
cc: pgsql-docs@postgresql.org
Subject: Re: a little fix for text search
In-reply-to: 
 <CAF4Au4w6rrH_j1bvVhzpOsRiHCog7sGJ3LSX0tY8ZdwhHT88LQ@mail.gmail.com>
References: 
 <CAF4Au4w6rrH_j1bvVhzpOsRiHCog7sGJ3LSX0tY8ZdwhHT88LQ@mail.gmail.com>
Comments: In-reply-to Oleg Bartunov <obartunov@gmail.com>
	message dated "Sat, 12 Nov 2016 23:25:20 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4876.1478983756.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 12 Nov 2016 15:49:16 -0500
Message-ID: <4877.1478983756@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

Oleg Bartunov <obartunov@gmail.com> writes:
> Hi there !
> I don't know when exactly it was improved, but following notice in
> https://www.postgresql.org/docs/current/static/textsearch-controls.html#T=
EXTSEARCH-HEADLINE
> is currently not needed.

> ts_headline uses the original document, not a tsvector summary, so it can
> be slow and should be used with care. A typical mistake is to call
> ts_headline for every matching document when only ten documents are to be
> shown. SQL subqueries can help; here is an example:

I don't see why that stopped being appropriate?  The point is that it
takes a raw text input which has to be re-parsed; that's still true
AFAICS.

			regards, tom lane


--=20
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs