thankyou very much.
but the method, you said, is adding a alias name, so it can not work.
and as i need to add many functions likes this, so the best way is to
compile the whole postgresql. eventhough, i did, it didnot work, so i am
puzzled, can add a function directly in the source file, and compile it, can
it work??
BTW: I have just seach the source for addingthe built-in function, and found
it need to add declaration in the include geo_decls.h, and add the function
in the geo_ops.c. can it not be enough??

On 5/1/07, Martijn van Oosterhout <[EMAIL PROTECTED]> wrote:

On Mon, Apr 30, 2007 at 11:05:35AM +0800, shieldy wrote:
> thankyou for your reply.
> I added it to the backend, because the internal ones such as
> function is keeped at there. so in my opinion, I just need to add a
> to the files, and then compile it. then we can use it as the internal
> bytheway, what's the backend file used for? I just didnot quite
> the postgresql.  and your meaning " place it in a module" , how should i
> do??

First, please reply to the list, not to me directly.

Secondly, just because you add it to the backend doesn't mean you can
use it straight away. There are thousands of functions in postgresql you
can't access from SQL, you have to declare them. See here:

Finally, by putting it in the backend you have to rebuild postgres
every time you want to change a function. Complete waste of time as
postgres can load external modules. See here:

Or better, just read the whole "Extending SQL" section.

Have a nice day,
Martijn van Oosterhout   <[EMAIL PROTECTED]>
> From each according to his ability. To each according to his ability to

Version: GnuPG v1.4.1 (GNU/Linux)


Reply via email to