-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I would like to know first, if I'm mistaken, or if external passwd files
are now specified in some other way, or must be enabled at compile time or
something like that; ie, am I doing something wrong?
The 7.3 Release Notes have the following items:
* Remove secondary password file capability and pg_password utility (Bruce)
* Add variable db_user_namespace for database-local user names (Bruce)
[...]
See the documentation for db_user_namespace:
hm. well, I can probably hack this to work, but I notice that the
documentations also says:
Note: This feature is intended as a temporary measure until a
complete solution is found. At that time, this option will be
removed.
so... how temporary is temporary? is it expected that the complete
solution will be at all similar? I don't want to spend a lot of time
building on this if the next upgrade will make it all obsolete again....
out of curiosity, why was the secondary password file capability removed?
I really liked the simplicity of being able to manage users completely
outside of the database, and to be able to do maintainence on the user
accounts without the database's even running.
anyway, thanks for the pointer - I'll start considering how I can use
db_user_namespace.
-Jason
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)
Comment: See https://private.idealab.com/public/jason/jason.gpg
iD8DBQFDE60bswXMWWtptckRAnGkAKDg96CVnZ55Oe0VANp2gDl1bojs5gCgltE4
2t985/6iyokjujrL9OUtHts=
=U30b
-----END PGP SIGNATURE-----
