I looked up about functions and schemas. I concluded the following:

1. The default schema when connecting to the database is public. (unless changed in configuration)
2. This can be changed for the duration of current connection by setting the search_path setting:

SET search_path TO myschema1, myschema2,...;

1. When any CREATE query is executed, the first schema in search_path becomes the object's schema.
2. If you want to use objects from more than one schema, either add those schemas to search_path or explicitly specify the schema name like public.myfunction.

Hence, this is not a bug in the code and does not need fixing.

Hey, Kishore! What about a few days holidays from computer? ;-)

Thank you for the "search_path" hint. I'm using it but didn't know that you can add multiple paths. That's nice! So I was always switching either the search_path or added "public" before function names.

I think pgRouting and PostGIS will always go to "public" schema. (And to be able to identify functions easier it would be nice to have some sort of namespace like ST_ and GRP_).

So the question is, is it enough to expect a user to set multiple search paths, or should we allow to set it in function arguments? Or do I make a problem where no problem is? ;-)

I might sound like a nerd, but holidays without computer is boring :)
Anyways, I found this issue is closely related to another issue #16. Applied a small patch to resolve that issue.