-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FATAL: database "dave" does not exist #139
Comments
The first time you open Postgres.app, it automatically creates a database named like your username. Apparently this database doesn't exist. There are a few possible reasons why this database doesn't exist:
There are a number of reasons why psql might be connecting to a different server:
|
I'm also getting this error. I'm using the 9.3.1.0-alpha1 pre-release. This is on OS X Mavericks.
I haven't changed my username. My previous Postgres installation isn't running (I force quit all instance of Postgres). |
Could you try connecting to the "postgres" database: If all that works, it seems that Postgresapp called initdb successfully, but createdb failed. You can do that manually, just execute |
also happened to me on a virgin Mavericks install. Had to PS. thanks for maintaining Postgres.app, I love it. |
This bug occurs for me as well using the Homebrew formula for installing PostgreSQL. Trace:
System:
|
happened to me as well on a Yosemite install while installing a rails app locally.
createdb USERNAME fixed the problem - thanks! |
I first tried with Homebrew then I ran into this error. Then uninstalled postgres by brew
|
is there a solution to this yet ? I am getting the same error |
just do like this: hope useful to you. |
When I type createdb USERNAME i get the response command not found, could you assist me? |
|
This should help people fix issues like #139
The new version of Postgres.app now checks if the port is in use before attempting to init a server and create a database. This makes it much less likely to fail. Additionally, Postgres.app displays more reasonable error messages when a problem occurs. And finally, the troubleshooting section in the docs now explains how to fix this problem. |
|
For me as well, "database doesn't exist" error was showing up. While trouble shooting I figured that I accidentally dropped the database with my name that Postgresapp creates while initialising. I simply created one database with my name and things were fine. Thus, I assume that every time I launch the Postgresapp it checks connection for the database with my name. Please correct me if I am wrong. Thanks in advance. |
thank you so mucccch |
using the "psql" menu item (OSX 10.8.4) I get
Last login: Sat Oct 19 07:59:28 on ttys009
/Applications/Postgres.app/Contents/MacOS/bin/psql ; exit;
Daves-MacBook-Pro:~ dave$ /Applications/Postgres.app/Contents/MacOS/bin/psql ; exit;
psql: FATAL: database "dave" does not exist
logout
[Process completed]
The text was updated successfully, but these errors were encountered: