> would be the right solution to make tsearch V2 to be fully incompatible
> with old tsearch (so both version could live in one database) and
> release tsearch v2 in separate directory. This way require some additional
> work but would not confuse people. As a bonus, people could start playing
> with new tsearch V2 very easy.
That seems like the best way.
I guess what we need to do is build it in to Postgres at some point, so
people won't have these problems...
Chris
