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 796269FA7B6 for ; Mon, 26 Jun 2006 18:07: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 14224-10 for ; Mon, 26 Jun 2006 18:06:54 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 8BD179FA6B3 for ; Mon, 26 Jun 2006 18:06:52 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k5QL6nZQ022974; Mon, 26 Jun 2006 17:06:49 -0400 (EDT) To: carlosreimer@terra.com.br cc: rodrigo.sakai@zanthus.com.br, pgsql-admin@postgresql.org Subject: Re: RES: Hiding table structure information In-reply-to: References: Comments: In-reply-to "Carlos H. Reimer" message dated "Mon, 26 Jun 2006 17:48:11 -0300" Date: Mon, 26 Jun 2006 17:06:49 -0400 Message-ID: <22973.1151356009@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/244 X-Sequence-Number: 22206 "Carlos H. Reimer" writes: > Maybe the question should be reformulted to: is there a way to hide > pg_catalog schema? There is not. My advice would be to put clients in separate databases if you need that much isolation between them. regards, tom lane