X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 62FE8554D6 for ; Thu, 24 Feb 2005 15:45:28 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 69827-04 for ; Thu, 24 Feb 2005 15:45:26 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id C776E5549E for ; Thu, 24 Feb 2005 15:45:25 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j1OFjYYL025158; Thu, 24 Feb 2005 10:45:34 -0500 (EST) To: Alex Gutman Cc: pgsql-admin@postgresql.org Subject: Re: Preventing changes to default settings of a collective account? In-reply-to: <20050224133308.9C99FC248@usenagutmanx2l.lss.emc.com> References: <20050224133308.9C99FC248@usenagutmanx2l.lss.emc.com> Comments: In-reply-to Alex Gutman message dated "Thu, 24 Feb 2005 08:33:08 -0500" Date: Thu, 24 Feb 2005 10:45:34 -0500 Message-ID: <25157.1109259934@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/285 X-Sequence-Number: 16453 Alex Gutman writes: > (The NOCREATEUSER option used when creating the collective user does > prevent it from changing its own password via > ALTER USER guest WITH ... PASSWORD ... You think so? This approach is doomed to failure --- the system sees no reason not to allow a user to change his own configuration, including his password. > Is there any way I could achieve my goal? Use more than one username. regards, tom lane