(postgres) FATAL: database "DATABASE_NAME" does not exist

[joshskidmore]

I had working Postgres connection stored in my config. Today, when I attempted to run a command, DB1 prompted me to connect to a database, I selected one of the (previously working) connections, and then received the following error:

DB1 Error: An error occured while connecting to the selected host.

FATAL: database "DATABASE_NAME" does not exist

DATABASE_NAME wasn't an actual database name, but DB1 never prompted me to connect to a database. Interestingly, DATABASE_NAME was the name of the Postgres user I entered.

Any ideas?

[gilbertw1]

This is pretty lame. Plugin has been unusable for me for almost a month and this issue continues to go completely ignored.

[joshskidmore]

This is disappointing because the plugin was great before it stopped working on a subsequent update.

This would not be so much of an issue if I hadn't spent $30 for this plugin, have it stop working, then get no response from the author or support team. I submitted this issue over twenty days ago, and I've recently tried to contact the author via email and have not received any response.

[alexggordon]

@gilbertw1 @joshskidmore

Hey you guys, working through a couple of different things. First off, I've had a couple people report this issue, but it's very selective, and definitely isn't an issue for most people.

In addition to that, since there isn't a "debug" feature (yet) I've had some problems actually diagnosing what's going on. Would either of your mind looking in your DB1 Sublime Settings and posting the results here (with any personal information removed)?.

[joshskidmore]

Here's my config ('X' = personal details):

{
  "db1_license_code": "DB1-XXXXX-XXXXX-XXXXX-XXXXX",
  "db1_license_email": "josh@XXXXX",
  "db1_license_name": "Josh Skidmore",
  "show_db1_header": true,
  "stored_connections":
  {
    "XXXXX@XXXXX.us-east-1.rds.amazonaws.com":
    {
      "database_type": "PostgreSQL",
      "password": "XXXXXXXXXXXXXXXXXXXX",
      "port": null
    },
    "XXXXX@XXXXX.us-east-1.rds.amazonaws.com":
    {
      "database_type": "PostgreSQL",
      "password": "XXXXXXXXXXXXXXXXXXXX",
      "port": null
    }
  }
}

[alexggordon]

Hey @joshskidmore:

So I've done some of digging around, and I'm wondering if it has something to do with Amazon's configuration of Postgresql (it's actually technically a fork of PG).

Could you fixing the "port" key, and adding the "connection_timeout" param?

It should look similar to this afterwards.

    "XXXXX@XXXXX.us-east-1.rds.amazonaws.com":
    {
        "database_type": "PostgreSQL",
         "password": "XXXXXXXXXXXXXXXXXXXX",
         "port": 5432,
         "connection_timeout": 10
     }

I've had problems with timeouts to Amazon's postgres servers before, and I'm curious if that might be an issue.

[joshskidmore]

I added the port and connection_timeout parameters, and still no luck. I continue to get "FATAL: database "XXXXXX" does not exist. And in this case, the database name it appears DB1 is attempting to connect to is the same as the username specified in the connection profile.

[joshskidmore]

Just checking in on this. Any updates?

[joshskidmore]

Any updates?

[gilbertw1]

Looks like this project is dead.