pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Goulet, Dick <DGoulet@vicr.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alex Gutman <agutman@emc.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Preventing changes to default settings of a collective
Date: Thu, 24 Feb 2005 11:43:58 -0600
Message-ID: <1109267038.30529.185.camel@state.g2switchworks.com> (raw)
In-Reply-To: <4001DEAF7DF9BD498B58B45051FBEA65022E0324@25exch1.vicorpower.vicr.com>
References: <4001DEAF7DF9BD498B58B45051FBEA65022E0324@25exch1.vicorpower.vicr.com>
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 <agutman@emc.com> 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
view thread (5+ messages) latest in thread
Message-ID: <1109267038.30529.185.camel@state.g2switchworks.com> Permalink: ../1109267038.30529.185.camel@state.g2switchworks.com/ Also on: postgresql.org/message-id/1109267038.30529.185.camel@state.g2switchworks.com ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients from your mail client; the link fills in the headers below: reply via email Some clients, webmail especially, drop In-Reply-To and References from a link, and the reply then starts a new thread: use the mbox below. To: pgsql-admin@postgresql.org Cc: smarlowe@g2switchworks.com, DGoulet@vicr.com, tgl@sss.pgh.pa.us, agutman@emc.com Subject: Re: Preventing changes to default settings of a collective In-Reply-To: <1109267038.30529.185.camel@state.g2switchworks.com> References: <4001DEAF7DF9BD498B58B45051FBEA65022E0324@25exch1.vicorpower.vicr.com> <1109267038.30529.185.camel@state.g2switchworks.com> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox