[Gnumed-devel] bootstrapping needs to be more flexible ?

[Syan Tan]

I'm running debian with postgresql 8.0 , and I can do a command line createlang plpgsql gnumed_v2  if I am logged in as postgres,

but the python script that looks for where the plpgsql lib module is inorder to do the sql " create language plpgsql call_handler ..."

fails, because it can't find the call handler lib.  This sql command is damn ugly anyway, needing to try to guess what the physical

path is anyway, so what about an alternate execution path for running createlang ?

I still think it's absurd that the bootstrapping process doesn't check pg_hba.conf and postgresql.conf  for you anyway, and offer to fix it,

because you've got to run it as root anyway, so anyone who could bootstrap  can easily do "su postgres" and alter /drop /create

anything anyway.

  I think the sql scripts should be designed to be idempotent, so you can do away with "set on_error_stop 1" , and any inserts  include

all values including the primary key value, so the bootstrapping is more robust and doesn't choke.

well that's my xmas scrooge.  Bah humbug !