agora inbox for pgsql-sql@postgresql.org  
help / color / mirror / Atom feed
From: Julien Cigar <jcigar@ulb.ac.be>
To: Campbell, Lance <lance@illinois.edu>
Cc: pgsql-sql@postgresql.org <pgsql-sql@postgresql.org>
Subject: Re: best strategy for searching large text fields
Date: Fri, 31 Oct 2014 16:17:10 +0100
Message-ID: <20141031151710.GD8131@mordor.lan> (raw)
In-Reply-To: <B75CD08C73BD3543B97E4EF3964B7D701FC6EC81@CITESMBX1.ad.uillinois.edu>
References: <B75CD08C73BD3543B97E4EF3964B7D701FC6EC81@CITESMBX1.ad.uillinois.edu>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-sql>

On Fri, Oct 31, 2014 at 02:59:48PM +0000, Campbell, Lance wrote:
> PostgreSQL 9.3.x
> I am looking for really good documentation on how to do the following.
> 
> Use Case
> I have a web application that will be storing into a table large blocks of HTML web content.  Users will then want to search these fields for phrases.  What is the best strategy for handling this in PostgreSQL?
> 
> What would the SQL look like?
> What data type should the web content field be in the table?
> Is there a way to set up the SQL so that matches are best match to least accurate match?
> Etc...
> 

FTS is the way to go:
http://www.postgresql.org/docs/9.3/static/textsearch-intro.html

> 
> 
> 
> Thanks,
> 
> Lance Campbell<http://illinois.edu/person/lance;
> Software Architect
> Web Services at Public Affairs
> 217-333-0382
> [University of Illinois at Urbana-Champaign logo]<http://illinois.edu/;
> 
> 



-- 
Julien Cigar
Belgian Biodiversity Platform (http://www.biodiversity.be)
PGP fingerprint: EEF9 F697 4B68 D275 7B11  6A25 B2BB 3710 A204 23C0
No trees were killed in the creation of this message.
However, many electrons were terribly inconvenienced.

view thread (2+ messages)

Message-ID: <20141031151710.GD8131@mordor.lan>
Permalink:  ../20141031151710.GD8131@mordor.lan/
Also on:    postgresql.org/message-id/20141031151710.GD8131@mordor.lan

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: jcigar@ulb.ac.be, lance@illinois.edu
  Subject: Re: best strategy for searching large text fields
  In-Reply-To: <20141031151710.GD8131@mordor.lan>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox