Received: from mail4.zotnet.com (216-99-218-131.dsl.aracnet.com [216.99.218.131]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f7NIqRP68281 for ; Thu, 23 Aug 2001 14:52:27 -0400 (EDT) (envelope-from zot@zotconsulting.com) Received: from zotconsulting.com (216-99-218-134.dsl.aracnet.com [216.99.218.134]) by mail4.zotnet.com (Postfix) with ESMTP id 4987E13599 for ; Thu, 23 Aug 2001 11:43:24 -0700 (PDT) Message-ID: <3B8550E9.3BC47EA7@zotconsulting.com> Date: Thu, 23 Aug 2001 11:52:25 -0700 From: "Zot O'Connor" X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16 i686) X-Accept-Language: en MIME-Version: 1.0 To: "pgsql-sql@postgresql.org" Subject: Execute permsissions on fuctions Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200108/294 X-Sequence-Number: 4540 Other SQL servers have the concept of stored procedures having different permissions. For instance a procedure that can update a table. Since a web site typically connects as the webuser (or equiv postgres user), I do not want to offer update to the webuser. The way I have done this elsewhere is to create a stored procedure that could update the table, and allow the webuser to update the table. The procedure had perms of a user who could update the table, but the webuser could not. How can I do this in Postgres? Thanks. -- Zot O'Connor http://www.ZotConsulting.com http://www.WhiteKnightHackers.com