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 611DA9FA7B6 for ; Mon, 26 Jun 2006 18:07:31 -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 16869-07 for ; Mon, 26 Jun 2006 18:07:09 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170]) by postgresql.org (Postfix) with ESMTP id B2D329FA6B3 for ; Mon, 26 Jun 2006 18:07:09 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id a2so2258037ugf for ; Mon, 26 Jun 2006 14:07:06 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=YGCMe82b5q21TP/nabjWfwA7sVXDJw0GbEm1ukbq9TjHtl1iZxpYIdukznGvB0ZVnwAv2hz6yn6j7FRe9Jro+71n5uHgV9Zw+tLGFOQggk0DjSp0xDXSv+txsHJxuR70Y5x36ZTm6eP3flQjM1Y9StndkgJoz8Gi6K+wMEdYySw= Received: by 10.66.240.12 with SMTP id n12mr5366915ugh; Mon, 26 Jun 2006 14:07:06 -0700 (PDT) Received: by 10.67.98.11 with HTTP; Mon, 26 Jun 2006 14:07:06 -0700 (PDT) Message-ID: <36e682920606261407i69287262n4942f7c9642f552e@mail.gmail.com> Date: Mon, 26 Jun 2006 17:07:06 -0400 From: "Jonah H. Harris" To: carlosreimer@terra.com.br Subject: Re: Hiding table structure information Cc: rodrigo.sakai@zanthus.com.br, pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <000301c6995b$7d5c9150$4700a8c0@TREEZANTHUS> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/245 X-Sequence-Number: 22207 On 6/26/06, Carlos H. Reimer wrote: > 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. You could use a set returning function and a view to hide the original table's details. As for hiding pg_catalog... I believe you could create a rule on it. Never tried to hide something this extensively... and don't really understand a practical reason for doing so. Remember, security through obscurity is flawed from the get go. -- Jonah H. Harris, Software Architect | phone: 732.331.1300 EnterpriseDB Corporation | fax: 732.331.1301 33 Wood Ave S, 2nd Floor | jharris@enterprisedb.com Iselin, New Jersey 08830 | http://www.enterprisedb.com/