Re: tsearch2 in PostgreSQL 8.3?

Andrew Dunstan <andrew@dunslane.net>

From: Andrew Dunstan <andrew@dunslane.net>
To: Bruce Momjian <bruce@momjian.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@commandprompt.com>, Heikki Linnakangas <heikki@enterprisedb.com>, Oleg Bartunov <oleg@sai.msu.su>, Teodor Sigaev <teodor@sigaev.ru>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2007-08-15T03:38:28Z
Lists: pgsql-hackers

Bruce Momjian wrote:
>>
>> The people who actually use tsearch2 seem to all have the same opinion ...
>> so I think we can't go too far in the bullet-proofing direction.
>>     

Yeah.
>> But I would like a design that is bulletproof in dump/reload scenarios,
>> and I think it's fair to question that aspect of the tsearch2 design
>> because we've seen many reports of people having trouble updating
>> databases that use tsearch2.
>>     
>
> Yea, look at the trouble we are having trying to underestand it all.

True. But I wasn't too concerned about the forecast difficulties with 
data only dumps. Those fail in plenty of circumstances. It is important 
that there is *some* reliable dump/restore/upgrade path, though.

cheers

andrew