# 配置 Discourse 使用独立的 PostgreSQL 服务器

**URL:** https://meta.discourse.org/t/configure-discourse-to-use-a-separate-postgresql-server/46375
**Category:** Self-Hosting
**Tags:** how-to
**Created:** [2016年六月23日 23:48 UTC](https://meta.discourse.org/t/configure-discourse-to-use-a-separate-postgresql-server/46375 "2016-06-23T23:48:02Z")
**Posts on this page:** 1
**Showing post:** 52

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [2026年一月8日 18:17 UTC](https://meta.discourse.org/t/configure-discourse-to-use-a-separate-postgresql-server/46375/52 "2026-01-08T18:17:07Z")

</div>

我们上个月合并了一个拉取请求（PR）来处理这个问题，您使用的是最新版本吗？

> <https://github.com/discourse/discourse/pull/35070>
>
> On certain hosting environments (azure postgres flex notably) CREATE EXTENSION r…equires a high level of permissions if the extension in question is marked as "untrusted" by postgres. This level of permission might not be available at runtime if the database user has low privileges.
> 
> Unfortunately, the migration currently tries to CREATE EXTENSION even if the "vector" extension already exists, which causes an unavoidable permission error.
> 
> This PR just adds a check to see if "vector" is already present, and skips if it is.

---

_[View the full topic](https://meta.discourse.org/t/configure-discourse-to-use-a-separate-postgresql-server/46375)._