From: | "Edward W(dot) Rouse" <erouse(at)comsquared(dot)com> |
---|---|
To: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: lost password |
Date: | 2009-11-18 15:10:42 |
Message-ID: | 015b01ca6861$4b919930$e2b4cb90$@com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Well, the username and password are the same, but the md5 is different. But
it doesn't seem to matter because either one works the same. The fact that
you can have 2 different md5's yet still have the same user name and
password and have logins work is what I found to be interesting.
But my original problem is solved in either case, so it doesn't really
matter to me. I just found it to be ... interesting.
Edward W. Rouse
-----Original Message-----
From: pgsql-sql-owner(at)postgresql(dot)org [mailto:pgsql-sql-owner(at)postgresql(dot)org]
On Behalf Of Tom Lane
Sent: Tuesday, November 17, 2009 6:57 PM
To: Edward W. Rouse
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: [SQL] lost password
"Edward W. Rouse" <erouse(at)comsquared(dot)com> writes:
> After I copied the md5 over I played around a bit and found the for the
> process user. I then used the alter user sql statement and rechecked the
> md5. It was different, but I could still use the same password to log in.
> Needless to say, I am a bit confused by that, but it works and that's what
I
> need.
The md5 will depend on both the actual password and the user's name
... does that help?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Another Trad | 2009-11-18 16:55:16 | need nelp with aggregate functions |
Previous Message | Tom Lane | 2009-11-17 23:56:46 | Re: lost password |