[$] Program names and "pollution"

A Linux user's $PATH likely contains well over a thousand differentcommands that were installed by various packages. It's not immediatelyobvious which package is responsible for a command witha generic name, like createuser. There are ways to figure it out, ofcourse, but perhaps it would make sense for packages like PostgreSQL, whichis responsible for createuser, to give their commands names thatare less generic-and more easily disambiguated-such aspg_createuser. But renaming commands down the road has "backwardcompatibility problems" written all over it, as a recent discussion on the pgsql-hackers mailinglist shows.