| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: TSearch2 performance issue? |
| Date: | 2005-04-01 15:58:45 |
| Message-ID: | 424D6FB5.8010608@familyhealth.com.au |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
It's a bit tricky, since the machine I noticed it on is in production -
how would I test this on a test machine with little data?
Should I put the 8.0 tsearch2.so on my 7.4 production server?
Chris
Teodor Sigaev wrote:
> I found several unpleasant blot in comparing functions and commit
> changes to 7.4, 8.0 and head. Pls check (it need just to recompile .so
> file)
>
> Christopher Kings-Lynne wrote:
>
>>> It's cached. This select should run only one time per connection for
>>> each used dictionary. If its'not then it's a bug. I'll check it.
>>
>>
>>
>> It probably is then - although I do use a persistent connection pool,
>> but I wouldn't have thought that'd use more than a new connection
>> every once in a while?
>>
>> Chris
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-04-01 16:22:59 | Re: ARC patent |
| Previous Message | Dave Held | 2005-04-01 15:49:26 | Re: ARC patent |