> Sorry my sheer ignorance here. I have already written a working, fully > tested - albeit unoptimised - implementation of this algorithm in Ruby, > accessible as a basic (HTTP GET) web service. However, a developer here > believes that the overhead of an HTTP connection over our gigabit LAN > will add too much to the (> 1 second) running time of the calculations. > This means that for political reasons we are forced to rewrite it as a > stored procedure that we can call directly from application code. The > project is urgent, the aforementioned developer is now on holiday, and > so my non-developer boss is scrabbling to learn PL/pgsql and I am forced > to bombard the list with inane questions. Thanks for your patience :) Use plperl :) (seriously). Or plruby, there is one. Joshua D. Drake > > Ashley > > > > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match > -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/