Re: Eeek! Major problem after reload with tsearch2

From: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
To: Karl Denninger <karl(at)denninger(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Eeek! Major problem after reload with tsearch2
Date: 2005-02-03 21:23:02
Message-ID: Pine.GSO.4.62.0502040019560.20328@ra.sai.msu.su
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

This is know issue with OIDS.
You,probably, needed to apply regprocedure_7.4.patch.gz
patch from http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/

Oleg
On Thu, 3 Feb 2005, Karl Denninger wrote:

> Ok, I found out what was going on with the tsearch2 module and reloading
> after an upgrade to 8.0.1 from 7.4.1
>
> The data now loads cleanly, and selects are fine.
>
> HOWEVER, when I attempt an update, I issue the following SQL command (this
> table has a tsearch2 vector in it:)
>
> update post set invisible='0' where ordinal='2843'
>
> And get back:
>
> ERROR: cache lookup failed for function 36476 CONTEXT: SQL statement
> "select lt.tokid, map.dict_name from public.pg_ts_cfgmap as map,
> public.pg_ts_cfg as cfg, public.token_type( $1 ) as lt where lt.alias =
> map.tok_alias and map.ts_name = cfg.ts_name and cfg.oid= $2 order by
> lt.tokid desc;"
>
> Aieeee!
>
> A reindex did nothing.
>
> What did I miss? Looks like there's something missing, but what?!
>
> --
>

Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Karl Denninger 2005-02-03 21:42:48 Re: Eeek! Major problem after reload with tsearch2
Previous Message Rory Campbell-Lange 2005-02-03 21:13:57 Re: Select from function for part of column results