On Friday 23 September 2005 01:51, Scott Marlowe seinde rooksignalen:
> Instead of using a general purpose account, why not give everyone an
> account, then make them a member of a group, and give that group the
> That way you can easily add / remove people from the group instead of
> trying to do it this way.
not an option, its for scripting and testing purposes
> Otherwise, don't use a password, set the machine to use trust or ident or
> something like that where a password wouldn't matter.
although it is then a user/pasword known by a lot of people,
it is still beter than no password
> -----Original Message-----
> From: pgsql-admin-owner(at)postgresql(dot)org on behalf of Wim Bertels
> Sent: Thu 9/22/2005 6:13 PM
> To: pgsql-admin(at)postgresql(dot)org
> Subject: [ADMIN] alter user
> any user can change his own password,
> i haven't found a way of prohibiting this.
> what about a general user (eg test/test), that is used by many people,
> one of those people could use alter user (being connected as test/test) the
> change the password, leaving the rest clueless..
> suggestions to prevent this?, i need a general (readonly) user!
In response to
pgsql-admin by date
|Next:||From: Bruce Momjian||Date: 2005-09-23 03:05:49|
|Subject: Re: [HACKERS] How to determine date / time of last postmaster|
|Previous:||From: Steuckrath, Randy A||Date: 2005-09-23 00:29:59|
|Subject: PgAdmin3 1.2.2 Install on Win32 Disrupts Pg Service|