> momjian(at)postgresql(dot)org writes:
> > Mention createlang when language not installed, per problem report.
> I think this is inappropriate. It's quite possible that an ordinary user
> is trying to create a function in a non-existent language, and he won't
> have the authority to use createlang. Or the language name is a typo and
> the language doesn't exist at all. Or the language is provided by a third
> party and createlang doesn't support it.
> You will find that almost nowhere a program will report 'foo not found --
> use bar to install it' because 'foo' missing might be fully intentional.
> (Or otherwise one might ask, if the program knows how to fix the
> situation, why doesn't it do so itself?)
> A user that has problems in this area can read the CREATE FUNCTION man
> page and find a reference to createlang there (or should find one).
But people report this error all the time and obviously don't understand
they need to use createlang. Doesn't hurt to point them to it. If it
is a typo, they will figure it out.
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
In response to
pgsql-committers by date
|Next:||From: tgl||Date: 2001-10-13 23:32:34|
|Subject: pgsql/src backend/utils/adt/numeric.c backend/ ...|
|Previous:||From: Peter Eisentraut||Date: 2001-10-13 19:23:27|
|Subject: Re: pgsql/src/backend/commands define.c|