Error Role Postgres Does Not Exist
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this role doesn't exist postgres site About Us Learn more about Stack Overflow the company Business Learn
Role Postgres Does Not Exist Windows
more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question fatal role postgres does not exist x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up psql psql fatal role postgres does not exist fatal role does not exist up vote 5 down vote favorite 2 I recently the lastest version of ubuntu and i'm not used to it yet. I had several problems connecting postgresql with pgadmin3. I tryed to follow several tutorials to create a localhost server which I can use in pgadmin3. I didn't really hit the mark and I think I made it worse
Postgres Role Does Not Exist Mac
by installing, uninstalling, installing, uninstalling, trying answers I found... At this point I'm not sure my postgres is clean. It could be possible that I have two postgres installed, once again, I'm not sure. I tryed to uninstall it but I had an error which basicly said postgres wasn't in sudo. The thing is I now have this error running psql in the console : $psql psql: FATAL: role "user" does not exist I can't find the pg_hba.conf and at this point I'm too afraid to make things even worse by trying following any other posts. How could I make this work? postgresql ubuntu pgadmin share|improve this question edited Aug 9 at 17:03 Kasper Souren 4,21332661 asked Jan 29 '15 at 11:44 whiplash 30114 pg_hba.conf is irrelevant here. You are trying to connect with the username user - but that account/username/role does not exists. You need to specify an existing database user using the -U switch when starting psql –a_horse_with_no_name Jan 29 '15 at 11:47 Since the error message comes from psql, you are already connected to the DBMS, No need to mess with pg_hb
else has seen the same thing and knows of a simple fix. I get it when I run rake db:migrate or rake db:create db:migrate This is on MacOSX and the postgres app is installed. role does not exist postgres rails I found this topic on stack overflow: http://stackoverflow.com/questions/15301826/psql-fatal-role-postgres-does-not-exist So I can see that it's postgres role root does not exist probably a missing user of some sort. The stack overflow post mentions adding a superuser, so before I start messing with that,
Could Not Connect To Database Postgres Fatal Role Does Not Exist
hoping there's something else I can do. Thanks in advance! maco 2015-02-03 16:09:05 UTC #2 Stack Overflow's right. Postgres setup isn't complete. Kind of surprised the Postgress app doesn't create a postgres user within its own http://stackoverflow.com/questions/28213929/psql-fatal-role-does-not-exist database by default. Note, it's a superuser within Postgres, not for your whole system. If you're more familiar with MySQL, it's like how MySQL has its root user separate from your OS's root user. marlenac 2015-02-03 17:19:30 UTC #3 Thank you so much for the helpful reply. I will sort that out and update our wiki instructions with this "gotcha." On Tuesday, February 3, 2015, Maco
8.1 / 8.2 / 8.3 / 8.4 / 9.0 PostgreSQL 8.2.23 Documentation Prev Fast Backward Chapter 1. Getting Started Fast Forward Next 1.3. Creating a https://www.postgresql.org/docs/8.2/static/tutorial-createdb.html Database The first test to see whether you can access the database server is to try to create a database. A running PostgreSQL server can manage many databases. Typically, a separate database is used for each project or for each user. Possibly, your site administrator has already created a database for your use. He should have told you what the name of your database is. In does not that case you can omit this step and skip ahead to the next section. To create a new database, in this example named mydb, you use the following command: $ createdb mydb This should produce as response: CREATE DATABASE If so, this step was successful and you can skip over the remainder of this section. If you see a message similar to createdb: command not found does not exist then PostgreSQL was not installed properly. Either it was not installed at all or the search path was not set correctly. Try calling the command with an absolute path instead: $ /usr/local/pgsql/bin/createdb mydb The path at your site might be different. Contact your site administrator or check back in the installation instructions to correct the situation. Another response could be this: createdb: could not connect to database postgres: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/tmp/.s.PGSQL.5432"? This means that the server was not started, or it was not started where createdb expected it. Again, check the installation instructions or consult the administrator. Another response could be this: createdb: could not connect to database postgres: FATAL: role "joe" does not exist where your own login name is mentioned. This will happen if the administrator has not created a PostgreSQL user account for you. (PostgreSQL user accounts are distinct from operating system user accounts.) If you are the administrator, see Chapter 18 for help creating accounts. You will need to become the operating system user under which PostgreSQL was installed (usually postgres) to c