| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Johann Spies <jspies(at)sun(dot)ac(dot)za> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Full text search ts_heading strange result |
| Date: | 2012-07-26 14:41:38 |
| Message-ID: | 20408.1343313698@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Johann Spies <jspies(at)sun(dot)ac(dot)za> writes:
> On Thu, Jul 26, 2012 at 04:19:02PM +0800, Craig Ringer wrote:
>> You'll need to store language information alongside each text value
>> if you want to do anything more sophisticated.
> I was afraid that that will be the case :)
I'm not sure that there's anything horribly wrong with the strategy
of using "simple" for everything. You won't get language-aware stemming,
but maybe you don't need that. The problem with what you originally
posted was not that "simple" was inadequate, but that you weren't
applying it consistently --- you didn't have
default_text_search_configuration set to match.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joseph Marlin | 2012-07-26 14:59:07 | WAL tuning advice |
| Previous Message | Vincent Veyron | 2012-07-26 14:34:03 | Re: BI tools and postgresql |