# Adding pgvector to Fly Postgres

**URL:** <https://community.fly.io/t/adding-pgvector-to-fly-postgres/12202>\
**Category:** Fresh Produce\
**Tags:** postgres\
**Created:** [April 13, 2023, 2:56pm UTC](https://community.fly.io/t/adding-pgvector-to-fly-postgres/12202 "2023-04-13T14:56:29Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![jkonowitch](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/jkonowitch/32/17047_2.png) [@jkonowitch](https://community.fly.io/u/jkonowitch)\
**Post date:** [December 19, 2023, 3:21pm UTC](https://community.fly.io/t/adding-pgvector-to-fly-postgres/12202/17 "2023-12-19T15:21:38Z")

</div>

Heads up - [this documentation on fly.io](https://fly.io/docs/postgres/) has some out of date information.

> The Fly Postgres app is fully open source. Just fork [fly-apps/postgres-ha](https://github.com/fly-apps/postgres-ha) and add whatever meets your needs. You can even update an existing cluster with your new image using `fly deploy --image`. One caveat is that once you fork, you won’t be able to use `fly postgres` commands to administer your app.

`fly postgres` commands do indeed work with forked images. And, that git repo should likely point to [fly-apps/postgres-flex: Postgres HA setup using repmgr (github.com)](https://github.com/fly-apps/postgres-flex) instead of [fly-apps/postgres-ha: Postgres + Stolon for HA clusters as Fly apps. (github.com)](https://github.com/fly-apps/postgres-ha). And I wonder if the `postgres-ha` repo should get a deprecation notice. I spent some unnecessary time following those instructions, not realizing there was a new image.

---

_[View the full topic](https://community.fly.io/t/adding-pgvector-to-fly-postgres/12202)._