From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Richard Huxton <dev(at)archonet(dot)com> |
Cc: | Matroska80 <tloschiavo(at)adhocsistemi(dot)it>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Tsearch2 cache lookup problem |
Date: | 2006-03-08 21:26:23 |
Message-ID: | 17983.1141853183@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Nik | 2006-03-08 21:51:55 | Re: Out of memory error on pg_restore |
Previous Message | Tom Lane | 2006-03-08 21:19:42 | Re: pg_dump error - filesystem full |