> 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/managing-services-postgresql.md).

# Managing services

Core lifecycle actions — **Stop**, **Edit**, and **Delete** — are accessible from two places: the ellipsis icon (︙) on the My Services dashboard row, and the ellipsis icon on the database service home page.

***

## How do I stop a database service?

All active sessions are disconnected. Status transitions from **Stopping** → **Stopped**. Once stopped, the ellipsis icon shows a **Start** option to restart the service.

Both the database and the VM are stopped if there is only one service on it.

> **Note:**
>
> * Stop is unavailable when **stop protection** is enabled on the service.
> * Stop is not allowed when a DR/RR instance is attached to the service. DR/RR is an asynchronous replica compared to a synchronous HA setup, so stopping the primary could break replication continuity between primary and standby instances.
> * Use stop to reduce costs during development, testing, or training periods when the database is not needed.

### Steps to stop a service

1. Click the ellipsis icon (︙) next to the service → select **Stop**.
2. Optionally add comments explaining the reason.
3. Select the **Are you sure you want to continue?** checkbox.
4. Click **Stop**.

***

## How do I edit a database service?

The Edit service dialog lets you update:

| Setting                              | Description                                                                                        |
| ------------------------------------ | -------------------------------------------------------------------------------------------------- |
| **Service name**                     | Rename the database service                                                                        |
| **Description**                      | Update the free-text description                                                                   |
| **Enable delete protection**         | When enabled, blocks deletion to prevent accidental data loss (disabled by default)                |
| **Enable stop protection**           | When enabled, blocks the Stop action (disabled by default)                                         |
| **Enable auto minor version update** | When enabled, automatically applies minor version updates (toggle default depends on your service) |

### Steps to edit a service

1. Click the ellipsis icon (︙) → select **Edit**.
2. Make the required changes in the **Edit service** dialog.
3. Click **Update**.

***

## How do I delete a database service?

Deletion is permanent and irreversible — the confirmation dialog warns "This action cannot be undone. Please read carefully." You control whether the Availability Machine (snapshots, backups, WAL logs, DAPs) is retained after the service is deleted.

> **Note:** Delete is unavailable when **delete protection** is enabled on the service.

### Steps to delete a service

1. Click the ellipsis icon (︙) → select **Delete**.
2. (Optional) Select **Take a final snapshot before deletion** to create a standalone manual snapshot immediately before deletion.
   * Specify a name in **Snapshot Name**, or use the auto-generated name.
   * This snapshot is independent of the Availability Machine — it does not depend on retaining incremental backups, WAL logs, or the Availability Machine to remain usable.
   * A final snapshot does **not** support PITR, because PITR requires the WAL logs and incremental backup chain that are not preserved with this option.
3. Choose how to handle the **Availability Machine** using the **Retain existing data in the Availability Machine** checkbox:

   | Option                                                                                | What is retained                                                                                                                                                                                                                                                                                                                                                                                           |
   | ------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   | **Retain existing data** → All existing data (snapshots, backups, WAL logs, and DAPs) | Availability Machine and all its contents are retained and continue to age out per the existing RPO policy. Service Availability Machine and Azure/AWS NetApp Files volumes are also retained, and one snapshot is taken before the service is deleted. Manual snapshots are retained; automated snapshots and WAL logs are deleted per the SLA. Data access policies are retained until manually deleted. |
   | **Retain existing data** → Starred snapshots & backups only                           | Only starred snapshots and backups are kept; all other snapshots, backups, WAL logs, and DAPs are deleted, reducing the storage retained after deletion. For more information, see [Star a snapshot or backup](/tessell/database-engines/tessell-for-postgresql/db-services/am-postgresql-doc.md#how-do-i-star-or-unstar-a-snapshot).                                                                      |
   | **Do not retain** (checkbox cleared)                                                  | Availability Machine and all its contents — snapshots, DAPs, logs — are deleted across all regions.                                                                                                                                                                                                                                                                                                        |

   > If you selected **Take a final snapshot before deletion** in the previous step, that snapshot is retained independently, even if you clear this checkbox here.
4. Optionally, add comments.
5. Type the exact service name in the confirmation field.
6. Click **Delete**.


---

# 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/managing-services-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.