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 8D01552A52 for ; Thu, 24 Feb 2005 17:43:52 +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 37590-10 for ; Thu, 24 Feb 2005 17:43:49 +0000 (GMT) Received: from koolancexeon.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by svr1.postgresql.org (Postfix) with ESMTP id 38BCF52A55 for ; Thu, 24 Feb 2005 17:43:48 +0000 (GMT) Received: mail.g2switchworks.com 10.10.1.8 from 10.10.1.37 10.10.1.37 via HTTP with MS-WebStorage 6.5.6944 Received: from state.g2switchworks.com by mail.g2switchworks.com; 24 Feb 2005 11:43:58 -0600 Subject: Re: Preventing changes to default settings of a collective From: Scott Marlowe To: "Goulet, Dick" Cc: Tom Lane , Alex Gutman , pgsql-admin@postgresql.org In-Reply-To: <4001DEAF7DF9BD498B58B45051FBEA65022E0324@25exch1.vicorpower.vicr.com> References: <4001DEAF7DF9BD498B58B45051FBEA65022E0324@25exch1.vicorpower.vicr.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1109267038.30529.185.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Thu, 24 Feb 2005 11:43:58 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/289 X-Sequence-Number: 16457 Most of the time you have one login account, the problem would be better solved with a group. Most of the time... On Thu, 2005-02-24 at 11:36, Goulet, Dick wrote: > Collective user accounts are all well & good so long as everyone using > it understands that you don't change stuff. If you've got a user who is > adamant that they have to have a specific password, etc... Then your > only recourse is to create them their own user account. I've done that. > It's a bit painful, but a lot less than having the collective/generic > access account messed with. Therefore I agree wholeheartedly with Tom. > > -----Original Message----- > From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > Sent: Thursday, February 24, 2005 10:46 AM > To: Alex Gutman > Cc: pgsql-admin@postgresql.org > Subject: Re: [ADMIN] Preventing changes to default settings of a > collective account? > > 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 > > ---------------------------(end of broadcast)--------------------------- > TIP 7: don't forget to increase your free space map settings > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster