X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9D5FD5382F for ; Wed, 6 Apr 2005 06:54:11 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 19143-08 for ; Wed, 6 Apr 2005 05:54:07 +0000 (GMT) Received: from hetzner.co.za (lfw.hetzner.co.za [196.7.18.226]) by svr1.postgresql.org (Postfix) with ESMTP id C4AF6534FA for ; Wed, 6 Apr 2005 06:54:05 +0100 (BST) Received: from localhost ([127.0.0.1]) by hetzner.co.za with esmtp (Exim 4.50 (FreeBSD)) id 1DJ3UJ-0009SK-8n for pgsql-admin@postgresql.org; Wed, 06 Apr 2005 07:54:03 +0200 To: pgsql-admin@postgresql.org Subject: Preventing the schema from being revealed. From: Ian FREISLICH X-Attribution: BOFH Date: Wed, 06 Apr 2005 07:54:03 +0200 Message-Id: <20050406055405.C4AF6534FA@svr1.postgresql.org> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=2.196 tagged_above=0 required=5 tests=DNS_FROM_RFC_WHOIS, MSGID_FROM_MTA_ID X-Spam-Level: ** X-Archive-Number: 200504/69 X-Sequence-Number: 17082 Hi I have quite a complex database system and I want to expose a public interface to it without exposing my (and my company's) months of work. Is there a way to grant usage on a schema so that they can execute functions without allowing that user to view the structure of the database and the definitions of all the functions. Or is the only way to put wrapper functions in the public schema that are defined 'SECURITY DEFINER' so that they can execute functions in the api schema, that the public user does not have access to? I wouldn't mind them viewing the wrapper functions. -- Ian Freislich