Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UkZwX-0000XR-8A for pgsql-admin@arkaria.postgresql.org; Thu, 06 Jun 2013 13:09:29 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UkZwW-0006xq-F6 for pgsql-admin@arkaria.postgresql.org; Thu, 06 Jun 2013 13:09:28 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UkVhY-0002G1-IX for pgsql-admin@postgresql.org; Thu, 06 Jun 2013 08:37:44 +0000 Received: from tyo202.gate.nec.co.jp ([210.143.35.52]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UkVhR-0008QT-DE for pgsql-admin@postgresql.org; Thu, 06 Jun 2013 08:37:43 +0000 Received: from mailgate3.nec.co.jp ([10.7.69.195]) by tyo202.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id r568bYZv023289 for ; Thu, 6 Jun 2013 17:37:34 +0900 (JST) Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id r568bYs19002 for pgsql-admin@postgresql.org; Thu, 6 Jun 2013 17:37:34 +0900 (JST) Received: from gate.ntsp.nec.co.jp ([172.28.58.1]) by vgate01.nec.co.jp (8.14.4/8.14.4) with ESMTP id r568bXqs029501 for ; Thu, 6 Jun 2013 17:37:33 +0900 (JST) Received: from sea.ntsp.nec.co.jp (unknown [172.28.58.94]) by gate.ntsp.nec.co.jp (Postfix) with ESMTP id 6989F51449 for ; Thu, 6 Jun 2013 16:37:28 +0800 (PHT) Received: from sea.ntsp.nec.co.jp (localhost.localdomain [127.0.0.1]) by localhost (Email Security Appliance) with SMTP id 47EE6245B81E_1B04A48B for ; Thu, 6 Jun 2013 08:37:28 +0000 (GMT) Received: from relay.ntsp.nec.co.jp (unknown [172.28.58.2]) by sea.ntsp.nec.co.jp (Sophos Email Appliance) with ESMTP id 0A240245B62E_1B04A48F for ; Thu, 6 Jun 2013 08:37:28 +0000 (GMT) Received: from vmail.hq.ntsp.nec.co.jp (lvs-dir-2 [172.28.58.149]) by relay.ntsp.nec.co.jp (Postfix) with ESMTP id E9C0D51449 for ; Thu, 6 Jun 2013 16:37:27 +0800 (PHT) Received: from [172.28.60.144] (unknown [172.28.60.144]) by vmail.hq.ntsp.nec.co.jp (Postfix) with ESMTP id 70D021CBA27 for ; Thu, 6 Jun 2013 16:37:27 +0800 (PHT) Message-ID: <51B04A48.5000708@ntsp.nec.co.jp> Date: Thu, 06 Jun 2013 16:37:28 +0800 From: apagador User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Hide users not created by a user Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-email-security-tag: clean X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Hello all, For a multi-tenant database system, it is assumed that only databases and users created by a certain tenant should be accessible/viewable to him. From what I read, postgresql stores database and user information in catalogs that are accessible to public. Here is a scenario: Let's say Tenant A created a database and a set of users, and Tenant B also does the same in the same postgresql instance. Can postgresql limit the access/view to only those databases and users that Tenant A created? Any idea on how this could be done? Thanks and best regards. -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin