On Jun 10, 2014, at 8:26 AM, Vick Khera wrote:
Thanks so much for this.
We do a lot of searching on this column, so pre-computing seems to be the way.
I'm not worried about disk space for now, and can revisit that later if there
is a problem
Just for clarification on this:
Option A (less fas
Vick Khera wrote:
> Jonathan Vanasco wrote:
> Personally in these days of cheap disks I'd go with the dedicated
> column. Given that, you want to just have a GIN index on that one
> column, and the query you want, given some plain text string like
> "fluffy dog" is this:
>
> select plainto_tsqu
On Mon, Jun 9, 2014 at 8:55 PM, Jonathan Vanasco wrote:
> I can't figure out which one to use. This is on a steadily growing
> table of around 20MM rows that gets 20-80k new records a day, but existing
> records are rarely updated.
The question as always is a time-space trade-off. How
I'm having some issues with fulltext searching.
I've gone though the list archives and stack overflow, but can't seem to get
the exact answers. hoping someone can help.
Thanks in advance and apologies for these questions being rather basic. I just
felt the docs and some online posts are lea
