Hi.
I'm searching in a medium-sized table (135k rows, 29 columns). Some of the
records point to other (parent) records, whose data values have to be used
for filtering as well as for joins, instead of the record's own fields.
Grouping the different types of records into "subset" views, the query
On 2012-02-16 04:18, Adrian Klaver wrote:
> When you alter the role name you are told the password has been cleared. It
> would be fairly easy to wrap the rename and the setting of the password in a
> transaction.
But this shouldn't be necessary. I don't get why the salt has to be
linked with th
>From the manual:
| Because MD5-encrypted passwords use the role name as cryptographic
| salt, renaming a role clears its password if the password is
| MD5-encrypted.
In backend/commands/user.c
if (!pg_md5_encrypt(password, stmt->role, strlen(stmt->role),
encrypted_pa
