Re: text search vs schemas

Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> Uh, no. Function names for example are subject to search-path
>> confusion.

> Wait, are they? They are in PL languages but only because most
> languages store their source code as text just as is happening here.

Hmmm ... if you look at the current solution for default expressions
for serial columns, ie nextval() on a regclass constant, it's pretty
schema-safe. So we could imagine inventing a regconfig datatype that
is the same sort of wrapper-over-OID. Then make the 2-parameter form
of to_tsvector take that type instead of text.

That seems like it'd fix the problem for expression indexes on
to_tsvector calls, but I don't see how it fixes the problem for
triggers. We don't have any clear path for making trigger arguments
be anything but a list of strings.

regards, tom lane