Solving the 'FATAL: database does not exist' Error in PostgreSQL with Docker

Encountering a "FATAL: database does not exist" error when trying to connect to PostgreSQL in Docker? Discover how to troubleshoot and resolve this common issue effectively.
---

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Trying to run sql queries on postgres database in linux but get Fatal: database " db name " does not exist but docker ps shows it does exist

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Troubleshooting PostgreSQL Connection Issues in Docker

If you're trying to run SQL queries on a PostgreSQL database in a Linux environment using Docker, you may encounter a frustrating error message: "FATAL: database does not exist." This error can be bewildering, especially when you can see that your PostgreSQL container is running. Don’t worry; you’re not alone in facing this issue. In this guide, we'll explore the potential causes of this error and, more importantly, provide a clear, step-by-step guide on how to resolve it.

Understanding the Problem

You might be in a situation where you:

Run docker ps, which shows that your PostgreSQL container is up and running.

Use a command to access the PostgreSQL prompt, which works fine, confirming that you can interact with the database environment.

Attempt to connect to a database using a command like \c database_name, only to receive a "FATAL: database does not exist" error.

For instance, consider the following commands you might have executed:

Viewing Running Containers:

[[See Video to Reveal this Text or Code Snippet]]

Output shows your PostgreSQL container is active.

Accessing PostgreSQL Prompt:

[[See Video to Reveal this Text or Code Snippet]]

Prompt appears as postgres=# indicating success.

Attempting to Connect to Database:

[[See Video to Reveal this Text or Code Snippet]]

The unexpected error appears.

Identifying the Root Cause

The next step is investigating why this error occurs despite your database container being active. Here are some key points to consider:

1. Database Name Misalignment

In many cases, the database name you are trying to connect to may not match what is configured in your application environment. For instance, if you're using a Ruby on Rails application, the database name is often specified in the .env file but might not correspond with what you assume.

2. Naming Conventions

Confusion can arise due to naming conventions. The name you are trying to connect to might be slightly different from the expected format. For instance, you might be trying to connect to api-master_db_1, which is actually the Docker container's name, not the database name itself.

Solution Steps

To resolve the issue, follow these steps meticulously:

Step 1: Check the .env File

Locate your .env file associated with your application.

Verify the database name under the DATABASE_NAME configuration or similar keys. Ensure this is the name you intend to connect to through your SQL commands.

Step 2: List Existing Databases

Access the PostgreSQL prompt and execute the following command to list the available databases:

[[See Video to Reveal this Text or Code Snippet]]

This command will display all databases. Confirm whether the database you want to connect to is listed.

Step 3: Connect to the Correct Database Name

If the correct database name is different from what you initially attempted, use that name with the connection command instead:

[[See Video to Reveal this Text or Code Snippet]]

Step 4: Re-test Your Connection

Once you've confirmed the correct database name, attempt to connect again and run your intended SQL queries.

Conclusion

Encountering the "FATAL: database does not exist" error can be frustrating, but by following the structured approach outlined above, you can resolve it quickly. Always ensure that you are using the correct database name as specified in your configuration files and that it matches the databases available in your PostgreSQL instance.

If you still have questions or need further explanation regarding why there might be differences between your .env configurati