mirror of
https://github.com/supabase/supabase.git
synced 2026-10-06 01:45:10 +03:00
Utkarash Kumar Singh
432b339ff9
## What Two fixes to the **Ltree indexes require reindexing** and **Custom operator selectivity estimators** sections of the upgrade guide (added in #47003): 1. **ltree affected-check was incomplete.** The section only showed how to *find* ltree indexes — not how to determine whether the database is actually affected. A project on a single-byte (e.g. LATIN1) + `libc` database would run it, see its ltree indexes, and needlessly reindex. Added the canonical `reindex_required` check (multibyte encoding **or** non-`libc` collation provider) so unaffected users correctly see "no action needed." This matches the detection used in the customer email, the support playbook, and the dashboard upgrade warning. 2. **No version specified.** Neither section said which Postgres version it applies to. Added `_Applies when upgrading to Postgres 15.18 or 17.10._` to both. ## Notes - Docs-only change. - supa-mdx-lint + prettier clean. - Follow-up to #47003. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Updated upgrade guides for Postgres 15.18 and 17.10 with explicit applicability notes * Clarified the Ltree indexes reindexing workflow by adding an initial “reindex required” check before identifying affected indexes * Improved documentation for custom operator selectivity estimators with clearer version-specific guidance <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Reference Docs
Supabase Reference Docs
Maintainers
If you are a maintainer of any tools in the Supabase ecosystem, you can use this site to provide documentation for the tools & libraries that you maintain.
DocSpec
We use documentation specifications which can be used to generate human-readable docs.
- OpenAPI: for documenting API endpoints.
- SDKSpec (custom to Supabase): for SDKs and client libraries.
- ConfigSpec (custom to Supabase): for configuration options.
- CLISpec (custom to Supabase): for CLI commands and usage.
The benefit of using custom specifications is that we can generate many other types from a strict schema (eg, HTML and manpages). It also means that we can switch to any documentation system we want. On this site we use Next.js, but on Supabase's official website, we use a custom React site and expose only a subset of the available API for each tool.
Contributing
To contribute to docs, see the developers' guide and contributing guide.