On Friday 16 March 2007 04:44, Teodor Sigaev wrote:
> > I'm also concerned about the stability of the tsearch api in general wrt
> > including it in core.  Currently the recommended upgrade practice is to
> > dump/reload without tsearch, installing the new servers version of
> > tsearch
> That is because pg_ts* tables changes, function names and internal API.
> Putting tsearch in core discards a lot of such problem. For example, who
> notices changes in pg_am table from release to release? Really it was a
> developers/hackers, not a usual users

I've ran into problems on very vanilla setups that I am sure other users are 
going to run across... see the following for details: 

I don't see how the proposal is going to solve that type of problem, but maybe 
I am overlooking something?

Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to [EMAIL PROTECTED] so that your
       message can get through to the mailing list cleanly

Reply via email to