# Database access issues after upgrade v3.5.2 -\> v3.6.0.beta2

**URL:** <https://meta.discourse.org/t/database-access-issues-after-upgrade-v3-5-2-v3-6-0-beta2/387408>\
**Category:** Support\
**Created:** [November 2, 2025, 6:21pm UTC](https://meta.discourse.org/t/database-access-issues-after-upgrade-v3-5-2-v3-6-0-beta2/387408 "2025-11-02T18:21:56Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![Stew\_Pid](https://avatars.discourse-cdn.com/v4/letter/s/e68b1a/32.png) [@Stew\_Pid](https://meta.discourse.org/u/Stew_Pid)\
**Post date:** [November 8, 2025, 1:21am UTC](https://meta.discourse.org/t/database-access-issues-after-upgrade-v3-5-2-v3-6-0-beta2/387408/11 "2025-11-08T01:21:33Z")

</div>

I used apt to install the new extention and got it to work. Geez. Now to do proper backups and update to Postges 15. But, not tonight. 😉

My history seemed to get wiped so I can’t tell you exactly how I did that but beware. It requires postgres 13 and will try and reinstall that.

> **[Index of /vector/vector-0.8.1/sql/](https://api.pgxn.org/src/vector/vector-0.8.1/sql/)**

PS: Turns out I had turned on automatic backups but had forgotten about them. Not that I knew where they were. I’ll set up an rsync process to put them in the directory I do my other server backups too.

---

_[View the full topic](https://meta.discourse.org/t/database-access-issues-after-upgrade-v3-5-2-v3-6-0-beta2/387408)._