X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id A05E29FA7B6 for ; Mon, 26 Jun 2006 17:48:09 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 06770-08 for ; Mon, 26 Jun 2006 17:47:53 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from bungunia.hst.terra.com.br (bungunia.hst.terra.com.br [200.176.10.196]) by postgresql.org (Postfix) with ESMTP id C12309FA6B3 for ; Mon, 26 Jun 2006 17:47:53 -0300 (ADT) Received: from calivil.hst.terra.com.br (calivil.hst.terra.com.br [200.176.10.9]) by bungunia.hst.terra.com.br (Postfix) with ESMTP id 3EAAA3C74137; Mon, 26 Jun 2006 17:47:52 -0300 (BRT) X-Terra-Karma: -2% X-Terra-Hash: 0c3538790d2aa7e101aa4f4dab69170e Received-SPF: pass (calivil.hst.terra.com.br: domain of terra.com.br designates 200.176.10.9 as permitted sender) client-ip=200.176.10.9; envelope-from=carlosreimer@terra.com.br; helo=reimer; Received: from reimer (unknown [200.180.75.36]) (authenticated user carlosreimer@terra.com.br) by calivil.hst.terra.com.br (Postfix) with ESMTP id D7A011248120; Mon, 26 Jun 2006 17:47:51 -0300 (BRT) Reply-To: From: "Carlos H. Reimer" To: Cc: Subject: RES: Hiding table structure information Date: Mon, 26 Jun 2006 17:48:11 -0300 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <000301c6995b$7d5c9150$4700a8c0@TREEZANTHUS> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Importance: Normal X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/241 X-Sequence-Number: 22203 Yes, a but even so, if the client uses a tool like pgAdmin, he can see all the database structure. It?s because this kind of tool uses data from the pg_catalog schema. Maybe the question should be reformulted to: is there a way to hide pg_catalog schema? I think it can?t not be done because all metadata are there, but maybe somebody can see a solution. Thanks in advance, Reimer > -----Mensagem original----- > De: Rodrigo Sakai [mailto:rodrigo.sakai@zanthus.com.br] > Enviada em: segunda-feira, 26 de junho de 2006 17:03 > Para: carlosreimer@terra.com.br; pgsql-admin@postgresql.org > Assunto: RES: [ADMIN] Hiding table structure information > > > I think you have to use a view! You create a view on this table specifying > only the columns the user may have access, and then you give privileges on > this view instead of giving privileges on the table! > > > > -----Mensagem original----- > De: pgsql-admin-owner@postgresql.org > [mailto:pgsql-admin-owner@postgresql.org] Em nome de Carlos H. Reimer > Enviada em: segunda-feira, 26 de junho de 2006 14:40 > Para: pgsql-admin@postgresql.org > Assunto: [ADMIN] Hiding table structure information > > Hello, > > Is there a way to hide the table definition structure from an > user, even if > the user has privileges to select data from that table? > > Reimer > > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match > >