From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Matroska80 <tloschiavo(at)adhocsistemi(dot)it>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Tsearch2 cache lookup problem |
Date: | 2006-03-09 08:07:36 |
Message-ID: | 440FE248.1030404@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> Richard Huxton <dev(at)archonet(dot)com> writes:
>> Matroska80 wrote:
>>> Hi i have a problem using tsearch2 with postgresql. Executing:
>>> SELECT to_tsquery('default','kj');
>>> return a
>>> cache lookup failed for function 141542.
>
>> Try the following:
>> SELECT oid,* FROM pg_proc WHERE proname='to_tsquery';
>> That should show whether there is a function with that OID.
>
> My recollection is that older versions of tsearch2 use a configuration
> table that stores function OIDs. If you dump and restore that table
> verbatim then you'll get failures like this because the new installation
> has different OIDs for those functions. See the tsearch2 documentation
> for workarounds, but I think you're supposed to install tsearch2 before
> you restore the old dump.
Yes, you:
1. Create the db
2. Install tsearch2
3. do a pg_restore -l/-L and remove the tsearch2 elements when restoring.
However, Matroska80 did say that no dump/restore had occurred. That is
right, isn't it?
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2006-03-09 08:11:18 | Re: questions? |
Previous Message | Jussi Saarinen | 2006-03-09 07:49:16 | Re: 8.0 Client can't connect to 7.3 server? |