Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 502A6650078 for ; Mon, 18 Aug 2008 13:50:20 -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 23088-01 for ; Mon, 18 Aug 2008 13:49:50 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by postgresql.org (Postfix) with ESMTP id 507576503BF for ; Mon, 18 Aug 2008 13:49:51 -0300 (ADT) Received: by py-out-1112.google.com with SMTP id d37so1664513pye.29 for ; Mon, 18 Aug 2008 09:49:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=7+/A6ZuA0p1RTaLIJm0FVRL2e61R6zFoSU0oKUqX6WI=; b=uEBleeyQnNdnSJLuOtbAROinW4chi0fTITgj9z9XZGivBQiuXBmP/Kgx6rpEEH03yC RChUQSORpvzqCYn5mmXu488/WhKCB2lsl1fV3cYjRZkGiX+W/+O9pme+nStF+I+mC5SK vxABTto+J2ao3FayvnUSwVMljSd+CioafFZiw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=HD69/c4KwxssGi1pyGwei8tjaTqKBHG9Y4bZQdPr15yo+2V0MHi99Xv/4X4N+5jFVg akN9Ri38GuEXffy7TgtKWoRG6tqVo1CCWxx7+iHJLIVDkzpdA2JuynCCBu6v/hJv7uSw wV2kQT6HGeZYl+T3pLpW7gsly1KVXkbyou+0Q= Received: by 10.141.153.16 with SMTP id f16mr3414577rvo.17.1219078189695; Mon, 18 Aug 2008 09:49:49 -0700 (PDT) Received: by 10.141.197.1 with HTTP; Mon, 18 Aug 2008 09:49:49 -0700 (PDT) Message-ID: Date: Mon, 18 Aug 2008 10:49:49 -0600 From: "Scott Marlowe" To: "Thomas Jacob" Subject: Re: Best practice running a shared DB hosting server Cc: "Robert Treat" , pgsql-admin@postgresql.org In-Reply-To: <1219077495.18884.38.camel@enterprise.ims-firmen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1218635097.28547.28.camel@enterprise.ims-firmen.de> <1218642490.28547.50.camel@enterprise.ims-firmen.de> <200808181148.14557.xzilla@users.sourceforge.net> <1219077495.18884.38.camel@enterprise.ims-firmen.de> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200808/76 X-Sequence-Number: 29921 On Mon, Aug 18, 2008 at 10:38 AM, Thomas Jacob wrote: > I've changed my approach by revoking rights to schema public > from PUBLIC in the template1, and then granting all rights > to again just to the "main" user, and usage rights to > the additional users. > > So people aren't forced to use schemas. Not sure exactly what you mean. Everything in pgsql lives in a schema, whether it's public or another schema. By judicious use of the search_path settings you can make the use of such schemas nearly transparent to the users, but they're still there.