> It could not. I think the fundamental point here is that it is a real
> bad idea for the tsearch routines to make any assumptions about the
> current search path. What I would suggest is that the internal objects
> used by the tsearch routines (such as pg_ts_cfg) should be required to
> live in a specific schema ("tsearch2" seems like a good name) and that
> all the internal references inside the tsearch functions should be fully
> qualified names.
I think a better solution is to change tsearch2 to have two assumptions:
1. All tsearch2 objects will be loaded in the same schema, name not
important.
2. When an object foo is called and needs to refer to another object
bar, it should assume that bar exists in the same schema as foo, and NOT
in the current search_path.
Chris