From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>, <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: prevent users from seeing pl/pgsql code in pgadmin |
Date: | 2005-03-16 16:20:24 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E472BBC7@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
> -----Original Message-----
> From: pgadmin-hackers-owner(at)postgresql(dot)org
> [mailto:pgadmin-hackers-owner(at)postgresql(dot)org] On Behalf Of
> Merlin Moncure
> Sent: 16 March 2005 16:04
> To: pgadmin-hackers(at)postgresql(dot)org
> Subject: [pgadmin-hackers] prevent users from seeing pl/pgsql
> code in pgadmin
>
> Is there any relatively easy way to, uh, prevent your users
> from seeing
> some/all of your pl/pgsql code in pgAdmin? :) A by schema solution
> would be ideal.
Anything we did would be fairly pointless given that there's not much we
can do to stop them doing 'SELECT prosrc FROM pg_proc'. I suppose you
could remove select permissions from the table, but I wouldn't be
surprise if that broke things horribly - it certainly breaks pgAdmin and
pg_dump.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2005-03-16 16:33:00 | Re: prevent users from seeing pl/pgsql code in pgadmin |
Previous Message | Merlin Moncure | 2005-03-16 16:04:27 | prevent users from seeing pl/pgsql code in pgadmin |