Skip site navigation (1) Skip section navigation (2)

Re: Compiling pl/pgsql functions

From: Rod Taylor <rbt(at)rbt(dot)ca>
To: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
Cc: Rodrigo Sakai <rodrigo(at)2bfree(dot)com(dot)br>, pgsql-sql(at)postgresql(dot)org
Subject: Re: Compiling pl/pgsql functions
Date: 2004-02-19 16:48:02
Message-ID: 1077209281.25444.91.camel@jester (view raw, whole thread or download thread mbox)
Lists: pgsql-sql
> AFAIK there's not much you can do for obfuscation of pl functions right
> now since someone will be able to see the src text in pg_proc. However,
> are you allowing people that you don't want to see the code access to
> write arbitrary sql to the database?

This is another one of those items where it would be nice if users
didn't need access to read the system tables, but instead could rely on
the information schema (with extensions) to see what they own or have
access to use -- but nothing else.

Sometimes HR gets paranoid about billing seeing their business logic, or
lack thereof, but accounting needs to use both sets of information to do
their work.

Otherwise, having each group relegated to their own schema with
semi-public views is a nice way to pass information from department to
department for small companies. Sure beats the spreadsheets on the
central filer approach.

Rod Taylor <rbt [at] rbt [dot] ca>

Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
PGP Key:

In response to


pgsql-sql by date

Next:From: Rodrigo SakaiDate: 2004-02-19 17:05:21
Subject: Re: Compiling pl/pgsql functions
Previous:From: scott.marloweDate: 2004-02-19 16:38:09
Subject: Re: Distributed Transactions

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group