Re: text search parser, "uri"

Alvaro Herrera <alvherre@commandprompt.com> writes:
> I observed that the parser calls the part after the host in a URL,
> "uri".  This is quite incorrect; a URI is supposed to be a
> generalization of a URL, so it makes no sense to call that a URI.

I was wondering about that, but failed to go check :-(

> RFC 1738, section 3.1 calls that "url-path".
> My suggestion would be "url_path", with an underscore instead of an
> hyphen to be consistent with the hword_* names.

Works for me.  Please change it.
        regards, tom lane