Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id E0B1247604F for ; Mon, 6 Jan 2003 08:38:24 -0500 (EST) Received: from wolff.to (dsl093-249-074.chi3.dsl.speakeasy.net [66.93.249.74]) by postgresql.org (Postfix) with SMTP id 3927B476009 for ; Mon, 6 Jan 2003 08:38:24 -0500 (EST) Received: (qmail 11328 invoked by uid 500); 6 Jan 2003 13:50:19 -0000 Date: Mon, 6 Jan 2003 07:50:19 -0600 From: Bruno Wolff III To: Tambet Matiisen Cc: pgsql-sql@postgresql.org Subject: Re: Grant execute on functions; related objects permissions ? Message-ID: <20030106135019.GA11220@wolff.to> Mail-Followup-To: Tambet Matiisen , pgsql-sql@postgresql.org References: <81132473206F3A46A72BD6116E1A06AE1B14BA@black.aprote.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <81132473206F3A46A72BD6116E1A06AE1B14BA@black.aprote.com> User-Agent: Mutt/1.3.25i X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/34 X-Sequence-Number: 10899 On Mon, Jan 06, 2003 at 12:45:25 +0200, Tambet Matiisen wrote: > btw, views "execute" also with owner's rights, ie if you grant select on view, you do not have to grant select on every table used in view. Still current_user in view returns "caller", while maybe it should return owner? I don't think so. Knowing the caller is useful for granting access only to some rows that depend on which user is using the view.