> Because it's so full of obvious loopholes. Yes, > it might slow down > > someone who didn't have superuser access to the > database or root access > > to the machine it's on; but that doesn't count > as secure really. The > > problem is that the people who ask for this type of > feature are usually > > imagining that they can put their code on > customer-controlled machines > > and it will be safe from the customer's eyes. > Well, it isn't, and > > I don't think Postgres should encourage them to > think it is. > As much as I'm impressed with the "we do it properly or not at all" attitude, it'd be nice if there was an option to stop the casual user from viewing code. I'll admit to obfusicating bits and pieces using C, even though the function and everything it acts on are tied down with permissions. I understand in reality it provides no real extra security but somehow users being able to easily view something they don't have access to execute beyond it's name just feels wrong.
