On Tue, Jun 12, 2012 at 2:48 PM, Dave Page <dp...@pgadmin.org> wrote: > On Tue, Jun 12, 2012 at 1:35 PM, Kevin Grittner > <kevin.gritt...@wicourts.gov> wrote: >> Magnus Hagander wrote: >>> Kevin Grittner wrote: >> >>>> Are they running the installation as a system administrator? If >>>> so, rather than throwing up an error message and telling them to >>>> go use other tools to reset the password, is it possible for the >>>> administrator account to force a password change? If that is >>>> possible, it seems like it would be a lot more friendly. If not, >>>> perhaps the old postgres user could be renamed, and a new one >>>> created with the password? >>> >>> That might break another app running nuder that account. Such as a >>> different version of PostgreSQL... > > Right. > >>> But an option could be to create a different account to run it >>> under, I guess... Leaving the old one where it is. I think that's >>> better than renaming the old one, really. > > I'm not keen on adding additional user accounts - that's a security > problem imho. It'll leave the unaware user with multiple accounts on > the system, and may cause those that do understand what's going on > pain because they'll have to deal with multiple accounts for things > like server-side copy.
Oh, I certainly wouldn't do it without *informing* and verifying it with the user. > It also doesn't solve the problem during upgrades, though admittedly > that seems to be less common. Why do you need the account at all during upgrades? Don't you just stop the service and replace the binaries? -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
