Hello, > > These instructions do not seem to be about the password for an > individual users, but rather the instructions to allow clients and > users associated with clients to be allowed access - pgAdmin is one > of those?
Yes
> file, adding localhost and all users (followed guidance in the > manual) and then PostGreSQL wouldn't restart. When I run pgAdmin, it > presents me a password challenge, so that client seems to be > connected to the server. There are several command line references > to add new accounts, but they use unix commands (do those work in > windows, and how do I get to command line in windows)
Try psql. It should be there in bin directory under postgresql installation. For example - D:\Applns\PostgreSQL\8.4\bin
H:\>psql -U postgres Password for user postgres: psql (8.4.3) > one, or add a new user, and now have no documentation on what to do. > Why wouldn't pgAdmin know the default password for the user > "postgres" - I am not stupid, at least I don't think so, and would > know to change that right away. I am now having my doubts about > postgreSQL, as someone really should make this much simpler - > starting off on the wrong foot. > > Bottom line, how do I add a user with superuser privileges without > spending several hours reading online to start using this system? I > just want to log in folks, and create some databases and > tables...that should take like 2 minutes. Does anyone else think > this is ridiculous? Help please. You could try having just one line in the hba file? local all all trust
Then you could add users with passwords.... and have an entry similar to host all all 192.168.0.0/16 md5
"The information in this e-mail and any attachment is intended only for the person to whom it is addressed and may contain confidential and/or privileged material. If you have received this e-mail in error, kindly contact the sender and destroy all copies of the original communication. IBS makes no warranty, express or implied, nor guarantees the accuracy, adequacy or completeness of the information contained in this email or any attachment and is not liable for any errors, defects, omissions, viruses or for resultant loss or damage, if any, direct or indirect."
