Skip to content

Commit

Permalink
docs: remove restart option
Browse files Browse the repository at this point in the history
resizing a compute does not always result in a restart
  • Loading branch information
danieltprice committed Feb 21, 2025
1 parent 596ab73 commit 7173a98
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 2 deletions.
2 changes: 1 addition & 1 deletion content/docs/extensions/pg-extensions.md
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,7 @@ ALTER EXTENSION vector UPDATE TO '0.7.0';
```

<Admonition type="important">
When Neon releases a new extension or new extension version, a compute restart is required to make the new extension or extension version available for installation or update. A compute restart may occur on its own due to Neon's default [scale to zero](/docs/introduction/scale-to-zero) behavior. However, if your compute never restarts because you disabled scale to zero or because your compute is constantly active, you may need to force a restart. To force a restart, you can issue [Restart endpoint](https://api-docs.neon.tech/reference/restartprojectendpoint) API call (a temporary [compute resize](/docs/manage/endpoints#edit-a-compute) will also resize your compute). Please be aware that restarting a compute temporarily interrupts any connections currently using the compute.
When Neon releases a new extension or new extension version, a compute restart is required to make the new extension or extension version available for installation or update. A compute restart may occur on its own due to Neon's default [scale to zero](/docs/introduction/scale-to-zero) behavior. However, if your compute never restarts because you disabled scale to zero or because your compute is constantly active, you may need to force a restart. To force a restart, you can issue [Restart endpoint](https://api-docs.neon.tech/reference/restartprojectendpoint) API call. Please be aware that restarting a compute temporarily interrupts any connections currently using the compute.

Extensions installations and updates are automatically applied to any read replica computes on the same branch as your primary compute the next time the read replica compute restarts.
</Admonition>
Expand Down
1 change: 0 additions & 1 deletion content/docs/manage/endpoints.md
Original file line number Diff line number Diff line change
Expand Up @@ -241,7 +241,6 @@ You can restart a compute using one of the following methods:
--header 'authorization: Bearer $NEON_API_KEY'
```
- Stop activity on your compute (stop running queries) and wait for your compute to suspend due to inactivity. By default, Neon suspends a compute after 5 minutes of inactivity. You can watch the status of your compute on the **Branches** page in the Neon Console. Select your branch and monitor your compute's **Status** field. Wait for it to report an `Idle` status. The compute will restart the next time it's accessed, and the status will change to `Active`.
- Temporarily resizing your compute or changing your autoscaling minimum or maximum compute size setting restarts a compute. For compute resize instructions, see [Edit a compute](/docs/manage/endpoints#edit-a-compute).

## Delete a compute

Expand Down

0 comments on commit 7173a98

Please sign in to comment.