> For the complete documentation index, see [llms.txt](https://docs.tessell.com/tessell/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tessell.com/tessell/database-engines/tessell-for-postgresql/db-services/readme-postgresql/homepage-postgresql/databases-postgresql.md).

# Databases

The Databases tab presents a tabular view of all databases created within your database service.

***

## What columns and statuses appear in the Databases table?

| Column                  | Description                                                                                 |
| ----------------------- | ------------------------------------------------------------------------------------------- |
| **Name**                | Database name — unique within your database service.                                        |
| **Status**              | Current runtime state of the database (see table below).                                    |
| **Created**             | Date and time the database was created.                                                     |
| **Connection Endpoint** | Hostname for the database; click **See Details** for Service URL, Host, Port, and Username. |

#### Database status reference

| Status       | Description                                                                           |
| ------------ | ------------------------------------------------------------------------------------- |
| **READY**    | The database is up and running. Connections are allowed once it reaches READY status. |
| **DOWN**     | The database is down. No connections are allowed.                                     |
| **STOPPED**  | The database is not running and is completely shut down.                              |
| **CREATING** | Database creation is triggered and the creation process is in progress.               |
| **DELETING** | Database deletion is triggered and the deletion process is in progress.               |
| **FAILED**   | Database start failed.                                                                |
| **STOPPING** | Database stop is triggered and the stopping process is in progress.                   |
| **STARTING** | Database start is triggered and the starting process is in progress.                  |

***

## How do I create or delete a database?

### Steps to add a database

1. Click **+ Add Database** (top-right of the Databases tab).

   > **Note:** Databases should always be added using the Tessell UI.
2. Specify a database name. A database name must start with a letter or underscore, contain only alphanumeric characters and underscores, and be at most 63 characters long.
3. Click **Add**.

As an alternative, use the **Code** button (bottom-left) to view, copy, or download the API call for adding a database in Shell, Python, Go, Java, JavaScript, or PowerShell.

### Steps to delete a database

Click the ellipsis icon on the right side of the database row → select **Delete**.

<div align="center"><img src="https://3421475909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNKiIctERJykfezXfUU2%2Fuploads%2Fgit-blob-2ddc37ddfd922b06f7aad3f48c781d6c2d3acced%2Fdatabases.png?alt=media" alt=""></div>

<p align="center"><em>Figure 1 — Databases tab</em></p>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tessell.com/tessell/database-engines/tessell-for-postgresql/db-services/readme-postgresql/homepage-postgresql/databases-postgresql.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
