Re: [GENERAL] Eeek! Major problem after reload with tsearch2

2005-02-03 Thread Oleg Bartunov
On Thu, 3 Feb 2005, Karl Denninger wrote: The patch is in the 8.0.1 version of Tsearch2 already. The problem is that I have a dump from a 7.4.1 database taken with the 8.0.1 pg_dumpall that I need to be able to get back online on 8.0.x. you had to apply patch to 7.4.1 db before dumping or use regp

Re: [GENERAL] Eeek! Major problem after reload with tsearch2

2005-02-03 Thread Karl Denninger
The patch is in the 8.0.1 version of Tsearch2 already. The problem is that I have a dump from a 7.4.1 database taken with the 8.0.1 pg_dumpall that I need to be able to get back online on 8.0.x. Is the only option to find all the functions in the tsearch.sql file, drop them by hand, remove all th

Re: [GENERAL] Eeek! Major problem after reload with tsearch2

2005-02-03 Thread Oleg Bartunov
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 t

Re: [GENERAL] Eeek! Major problem after reload with tsearch2

2005-02-03 Thread Tom Lane
Karl Denninger <[EMAIL PROTECTED]> writes: > 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 > ERROR: cache lookup failed for function 36476 I think that tsearch2's control tables contain function OIDs, which means that you can't ju

Re: [GENERAL] Eeek! Major problem after reload with tsearch2

2005-02-03 Thread Karl Denninger
If I remove the full-text indexing from the table involved (remove the indices and triggers) then the system is fine. Somehow, it appears that there's some kind of internal consistency problem with the tsearch2 package. Attempts to recreate the indices (after dropping them) fail with the same