[Bug]: Wrong docs for replacing postgres by pgvector (v0.21) when self-hosting

[cnmicha]

What happened?

The docs page https://docs.affine.pro/docs/self-host-affine/affine-self-hosted-0.21-upgrade-guide gives instructions that should be done when self-hosting AFFiNE. The postgres container should be replaced by pgvector.

The docs page says there's two ways: either downloading the new docker-compose.yml from the given link (and it will just work out of the box, or manually replacing the container image.

Issue 1: I chose downloading the new docker-compose.yml from the link given in the docs. However, the specified image is still the old postgres image. I expected it to be pgvector/pgvector:pg16.

As a workaround, I did this change manually. Is this correct?

Issue 2: Also, the docs for changing the image manually say it should be changed to e.g. pgvector:pg16. This image does not exist, what you probably mean is pgvector/pgvector:pg16.

Issue 3: In the GitHub release notes, clear indications are missing that the manual at https://docs.affine.pro/docs/self-host-affine/affine-self-hosted-0.21-upgrade-guide must be followed.

Distribution version

Linux

App Version

0.21

What browsers are you seeing the problem on if you're using web version?

No response

Are you self-hosting?

• Yes

Self-hosting Version

0.21

Relevant log output

Anything else?

No response

[affine-issue-bot]

Issue Status: 🆕 *Untriaged

*🆕 Untriaged

The team has not yet reviewed the issue. We usually do it within one business day.
Docs: https://github.com/toeverything/AFFiNE/blob/canary/docs/issue-triaging.md

^{_{This is an automatic reply by the bot.}}

[forehalo]

It's actually not a required step when upgrading to 0.21. We will update the doc later.