Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id F32E4650F25 for ; Wed, 2 Jul 2008 12:01:38 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 76423-03-4 for ; Wed, 2 Jul 2008 12:01:34 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id 0972E650EFF for ; Wed, 2 Jul 2008 12:00:30 -0300 (ADT) Received: from perhan.alvh.no-ip.org (190-95-31-93.bk17-dsl.surnet.cl [190.95.31.93]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m62F2HAn013822 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Jul 2008 08:02:25 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 58D5B47C7C; Wed, 2 Jul 2008 11:00:12 -0400 (CLT) Date: Wed, 2 Jul 2008 11:00:12 -0400 From: Alvaro Herrera To: sftf Cc: pgsql-admin@postgresql.org Subject: Re: Roles as objects in Postgres's security system Message-ID: <20080702150012.GQ18252@alvh.no-ip.org> References: <1898029110.20080702163044@mail.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1898029110.20080702163044@mail.ru> User-Agent: Mutt/1.5.18 (2008-05-17) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Wed, 02 Jul 2008 08:02:25 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200807/24 X-Sequence-Number: 29634 sftf wrote: > Hi! > My English is bad, so in short - why Postgres (and surprisingly > other's, like Oracle) lacks something like this: If it's missing, it's because it's not implemented. This may be because nobody has yet come to it, or because it has been decided that it will not be implemented for whatever reason. If the syntax you propose is part of the SQL standard, feel free to propose it. If it's not, you need to present a solid case for it to be implemented. If you propose it and there are no objections, it doesn't mean it will be implemented right away; it'll happen much sooner if you send a patch. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support