Merge branch 'latest' into 4634-feedback-page-docsself-hostedlatestupgradesminor-upgrade

Author: billy-the-fish

_partials/_livesync-terminal.md

@@ -175,7 +175,7 @@ instance to a $SERVICE_LONG:
    As you run the $PG_CONNECTOR continuously, best practice is to run it as a Docker daemon.
 
    ```shell
-   docker run -d --rm --name livesync timescale/live-sync:v0.4.0 run \
+   docker run -d --rm --name livesync timescale/live-sync:v0.7.0 run \
       --publication <publication_name> --subscription <subscription_name> \
       --source $SOURCE --target $TARGET --table-map <table_map_as_json>
    ```
@@ -330,7 +330,7 @@ EOF
    Use the `--drop` flag to remove the replication slots created by the $PG_CONNECTOR on the source database.
 
    ```shell
-   docker run -it --rm --name livesync timescale/live-sync:v0.4.0 run \
+   docker run -it --rm --name livesync timescale/live-sync:v0.7.0 run \
       --publication <publication_name> --subscription <subscription_name> \
       --source $SOURCE --target $TARGET \
       --drop

_partials/_since_0_4_0.md

@@ -0,0 +1 @@
+<Tag variant="hollow">Since [pg_textsearch v0.4.0](https://github.com/timescale/pg_textsearch/releases/tag/v0.4.0)</Tag>

_partials/_since_2_2_0.md _partials/_since_2_2_0.mdx_partials/_since_2_2_0.md renamed to _partials/_since_2_2_0.mdx

@@ -9,6 +9,39 @@ products: [cloud]
 
 All the latest features and updates to $CLOUD_LONG.
 
+## pg_textsearch improvements (v0.3.0 and v0.4.0)
+<Label type="date">January 16, 2026</Label>
+
+Tiger Cloud now includes significant improvements to `pg_textsearch`, bringing major gains in query performance, index size, and scalability as we move toward GA.
+
+**What’s new:**
+- **Block MAX-WAND ranked search (v0.3.0):**  
+  Introduces the Block MAX-WAND algorithm for ranked keyword search, delivering substantial performance improvements. Query performance is now competitive with the fastest Postgres-based search solutions, including ParadeDB.
+- **Posting-list compression (v0.4.0):**  
+  Reduces index sizes by **40% or more**, making `pg_textsearch` indexes smaller than ParadeDB in many cases.
+- **Improved partition handling (v0.4.0):**  
+  Fixes and stability improvements for indexes on tables with large numbers of partitions.
+
+Additional optimizations, including block compression and parallel indexing, are in progress as `pg_textsearch` continues its sprint toward GA.
+
+**Learn more:**
+- [pg_textsearch v0.3.0 release notes](https://github.com/timescale/pg_textsearch/releases/tag/v0.3.0)  
+- [pg_textsearch v0.4.0 release notes](https://github.com/timescale/pg_textsearch/releases/tag/v0.4.0)
+
+## Postgres 18 support
+<Label type="date">January 13, 2026</Label>
+
+Tiger Cloud now supports **Postgres 18**. All new services are created with Postgres 18 by default, and existing services will be able to upgrade to Postgres 18 over the next few weeks.
+
+**Postgres 18 highlights include:**
+- **Asynchronous I/O (AIO), including `io_uring` on Linux**, for significantly faster read-heavy workloads
+- **Faster, less disruptive major upgrades**, including improved `pg_upgrade` and the ability to **preserve planner statistics** across upgrades
+- **Virtual generated columns** (now the default for generated columns) and the **`uuidv7()`** function for better UUID indexing behavior
+- **Query performance improvements**, including expanded index usage (for example, skip-scan on multicolumn B-tree indexes) and **parallel GIN index builds**
+- **Security and operability enhancements**, including **OAuth 2.0 authentication support** and **page checksums enabled by default for new clusters**
+
+For more details about Postgres 18, check the [official announcement](https://www.postgresql.org/about/news/postgresql-18-released-3142/)
+
 ## 🧱 Terraform Support for S3 Source Connectors and pg_textsearch update
 <Label type="date">January 09, 2026</Label>
 

about/changelog.md

@@ -8,14 +8,18 @@ products: [cloud, self_hosted]
 
 import EA1125 from "versionContent/_partials/_early_access_11_25.mdx";
 import SINCE010 from "versionContent/_partials/_since_0_1_0.mdx";
+import SINCE040 from "versionContent/_partials/_since_0_4_0.mdx";
 import IntegrationPrereqs from "versionContent/_partials/_integration-prereqs.mdx";
 
 # Optimize full text search with BM25 
 
-$PG full-text search at scale consistently hits a wall where performance degrades catastrophically. 
+$PG full-text search at scale consistently hits a wall where performance degrades catastrophically.
 $COMPANY's [pg_textsearch][pg_textsearch-github-repo] brings modern [BM25][bm25-wiki]-based full-text search directly into $PG,
-with a memtable architecture for efficient indexing and ranking. `pg_textsearch` integrates seamlessly with SQL and 
-provides better search quality and performance than the $PG built-in full-text search.
+with a memtable architecture for efficient indexing and ranking. `pg_textsearch` integrates seamlessly with SQL and
+provides better search quality and performance than the $PG built-in full-text search. With Block-Max WAND optimization,
+`pg_textsearch` delivers up to **4x faster top-k queries** compared to native BM25 implementations. Advanced compression
+using delta encoding and bitpacking reduces index sizes by **41%** while improving query performance by 10-20% for
+shorter queries.
 
 BM25 scores in `pg_textsearch` are returned as negative values, where lower (more negative) numbers indicate better 
 matches. `pg_textsearch` implements the following:
@@ -73,7 +77,7 @@ You have installed `pg_textsearch` on $CLOUD_LONG.
 
 ## Create BM25 indexes on your data
 
-BM25 indexes provide modern relevance ranking that outperforms $PG's built-in ts_rank functions by using corpus 
+BM25 indexes provide modern relevance ranking that outperforms $PG's built-in ts_rank functions by using corpus
 statistics and better algorithmic design.
 
 To create a BM25 index with pg_textsearch:
@@ -109,21 +113,31 @@ To create a BM25 index with pg_textsearch:
    WITH (text_config='english');
    ```
 
-   BM25 supports single-column indexes only. 
+   BM25 supports single-column indexes only. For optimal performance, load your data first, then create the index.
 
 </Procedure>
 
 You have created a BM25 index for full-text search.
 
 ## Optimize search queries for performance
 
-Use efficient query patterns to leverage BM25 ranking and optimize search performance.
+Use efficient query patterns to leverage BM25 ranking and optimize search performance. The `<@>` operator provides
+BM25-based ranking scores as negative values, where lower (more negative) scores indicate better matches. In `ORDER BY`
+clauses, the index is automatically detected from the column. For `WHERE` clause filtering, use `to_bm25query()` with
+an explicit index name.
 
 <Procedure>
 
 1. **Perform ranked searches using the distance operator**
 
    ```sql
+   -- Simplified syntax: index is automatically detected in ORDER BY
+   SELECT name, description, description <@> 'ergonomic work' as score
+   FROM products
+   ORDER BY score
+   LIMIT 3;
+
+   -- Alternative explicit syntax (works in all contexts)
    SELECT name, description, description <@> to_bm25query('ergonomic work', 'products_search_idx') as score
    FROM products
    ORDER BY score
@@ -142,6 +156,8 @@ Use efficient query patterns to leverage BM25 ranking and optimize search perfor
 
 1. **Filter results by score threshold**
 
+   For filtering with WHERE clauses, use explicit index specification with `to_bm25query()`:
+
    ```sql
    SELECT name, description <@> to_bm25query('wireless', 'products_search_idx') as score
    FROM products
@@ -163,7 +179,7 @@ Use efficient query patterns to leverage BM25 ranking and optimize search perfor
    FROM products
    WHERE price < 500
      AND description <@> to_bm25query('ergonomic', 'products_search_idx') < -0.5
-   ORDER BY description <@> to_bm25query('ergonomic', 'products_search_idx')
+   ORDER BY score
    LIMIT 5;
    ```
 
@@ -342,17 +358,30 @@ Customize `pg_textsearch` behavior for your specific use case and data character
    threshold, it automatically flushes to a segment at transaction commit.
 
    ```sql
-   -- Set memtable spill threshold (default 800000 posting entries, ~8MB segments)
-   SET pg_textsearch.memtable_spill_threshold = 1000000;
+   -- Set memtable spill threshold (default 32000000 posting entries, ~1M docs/segment)
+   SET pg_textsearch.memtable_spill_threshold = 32000000;
 
    -- Set bulk load spill threshold (default 100000 terms per transaction)
    SET pg_textsearch.bulk_load_threshold = 150000;
 
    -- Set default query limit when no LIMIT clause is present (default 1000)
    SET pg_textsearch.default_limit = 5000;
+
+   -- Enable Block-Max WAND optimization for faster top-k queries (enabled by default)
+   SET pg_textsearch.enable_bmw = true;
+
+   -- Log block skip statistics for debugging query performance (disabled by default)
+   SET pg_textsearch.log_bmw_stats = false;
    ```
    <SINCE010 />
 
+   ```sql
+   -- Enable segment compression using delta encoding and bitpacking (enabled by default)
+   -- Reduces index size by ~41% with 10-20% query performance improvement for shorter queries
+   SET pg_textsearch.compress_segments = on;
+   ```
+   <SINCE040 />
+
 1. **Configure language-specific text processing**
 
    You can create multiple BM25 indexes on the same column with different language configurations:
@@ -387,11 +416,26 @@ Customize `pg_textsearch` behavior for your specific use case and data character
           WHERE indexrelid::regclass::text ~ 'bm25';
           ```
 
-      - View detailed index information
+      - View index summary with corpus statistics and memory usage
+          ```sql
+          SELECT bm25_summarize_index('products_search_idx');
+          ```
+
+      - View detailed index structure (output is truncated for display)
           ```sql
           SELECT bm25_dump_index('products_search_idx');
           ```
 
+      - Export full index dump to a file for detailed analysis
+          ```sql
+          SELECT bm25_dump_index('products_search_idx', '/tmp/index_dump.txt');
+          ```
+
+      - Force memtable spill to disk (useful for testing or memory management)
+          ```sql
+          SELECT bm25_spill_index('products_search_idx');
+          ```
+
 </Procedure>
 
 You have configured `pg_textsearch` for optimal performance. For production applications, consider implementing result 

use-timescale/extensions/pg-textsearch.md

@@ -38,8 +38,6 @@ CREATE TABLE conditions (
 );
 ```
 
-<CreateHypertablePolicyNote />
-
 This example also references values in another `locations` table using a foreign
 key constraint.
 
@@ -50,7 +48,6 @@ Time columns used for partitioning must not allow `NULL` values. A
 
 </Highlight>
 
-For more information on how to manage constraints, see the
-[$PG docs][postgres-createconstraint].
+For more information on how to manage constraints, see the [$PG docs][postgres-createconstraint].
 
 [postgres-createconstraint]: https://www.postgresql.org/docs/current/ddl-constraints.html

use-timescale/schema-management/about-constraints.md

@@ -32,6 +32,12 @@ You can create a read-only user to provide limited access to your database.
     CREATE ROLE readaccess;
     ```
 
+1.  Grant usage on the schema to allow access to objects within it:
+
+    ```sql
+    GRANT USAGE ON SCHEMA <SCHEMA_NAME> TO readaccess;
+    ```
+
 1.  Grant the appropriate permissions for the role, as required. For example, to
     grant `SELECT` permissions to a specific table, use:
 

use-timescale/security/read-only-role.md

@@ -0,0 +1,148 @@
+# WARP.md
+
+This file provides guidance to WARP (warp.dev) when working with code in this repository.
+
+## Repository Overview
+
+This is the Tiger Data documentation repository, containing the source content for https://www.tigerdata.com/docs/. Tiger Data (formerly Timescale) is a modern Postgres data platform for time series, events, analytics, and vector search. The documentation is written in Markdown with custom components and is built separately in a private Gatsby-based repository.
+
+## Development Workflow
+
+### Link Checking
+Run link checker locally:
+```bash
+npx markdown-link-check <file.md> --config mlc_config.json
+```
+
+### Linting Documentation
+The repository uses Vale for prose linting:
+```bash
+vale --glob='["_partials/**/*", "_troubleshooting/**/*", "about/**/*", "api/**/*", "getting-started/**/*", "mst/**/*", "navigation/**/*", "self-hosted/**/*", "tutorials/**/*", "use-timescale/**/*", "ai/**/*"]'
+```
+
+Vale configuration is in `.vale.ini` and uses Vale + Google style guides.
+
+### Markdown Linting
+Custom markdownlint rules are in `.vscode/markdownlint/` and configured via `.markdownlint.json` and `.markdownlint-cli2.jsonc`. These enforce documentation-specific patterns like:
+- Proper blank lines around `<Highlight>` blocks
+- Correct `<Procedure>` formatting
+- Proper frontmatter structure
+
+### Creating Hyperfunction Documentation
+Use the template generator script for new two-step aggregate hyperfunction groups:
+```bash
+npm run template:hyperfunction
+```
+
+This interactive script creates the directory structure and template files in `api/_hyperfunctions/`.
+
+### Bulk Editing API Excerpts
+Helper scripts in `.helper-scripts/` for bulk frontmatter editing:
+```bash
+cd .helper-scripts
+./extract-excerpts.sh  # Extract excerpts to single file
+# Edit extracted_excerpts.md
+./insert-excerpts.sh   # Update original files
+```
+
+## Architecture
+
+### Navigation Hierarchy
+Navigation structure is governed by `page-index/page-index.js` files throughout the repository. The top-level `page-index/page-index.js` imports and combines all section-level navigation files.
+
+**Page index structure:**
+- `href`: URL segment, must match markdown filename (without extension)
+- `title`: Page name in left TOC
+- `excerpt`: Short description (up to 100 chars) for page cards
+- `type`: Optional - `directory`, `placeholder`, `redirect-to-child-page`
+- `children`: Array of child pages
+- `pageComponents`: Display style for child pages - `['featured-cards']` or `['content-list']`
+- `index`: Specify alternative file if not `index.md`
+
+Major documentation sections:
+- `getting-started/` - Getting started guides
+- `use-timescale/` - Product usage documentation
+- `api/` - API references and hyperfunctions
+- `tutorials/` - Step-by-step tutorials
+- `integrations/` - Integration guides
+- `self-hosted/` - Self-hosted deployment docs
+- `mst/` - Timescale MST documentation
+- `ai/` - AI and vector search features
+- `migrate/` - Migration guides
+- `about/` - Company and product information
+
+### Content Organization
+
+**Partials (`_partials/`):** Reusable content snippets. Create files starting with underscore. Import into target `.mdx` pages.
+
+**Troubleshooting (`_troubleshooting/`):** Individual troubleshooting entries (not full pages). Each file contains frontmatter with:
+- `title`: Entry title
+- `section`: Must be `troubleshooting`
+- `products` and/or `topics`: Where entry appears (at least one required)
+- `errors`: Optional error display with `language` and `message`
+- `keywords`: Displayed at bottom, link to related pages
+- `tags`: Affect related page calculations (not displayed)
+
+Troubleshooting pages are programmatically assembled during build. If page doesn't exist, add entry in page-index with `type: "placeholder"`.
+
+**API Documentation (`api/`):** Function references include:
+- Function name with empty parentheses if takes arguments
+- Brief description with warnings
+- Usage samples demonstrating argument syntax
+- Argument table: `Name`, `Type`, `Default`, `Required`, `Description`
+- Return table: `Column`, `Type`, `Description`
+
+Hyperfunctions are organized in `api/_hyperfunctions/` with subdirectories for two-step aggregation pattern functions.
+
+### Custom Components
+
+Available formatting beyond standard Markdown:
+- `<Procedure>`: Step-by-step instructions with bold step summaries
+- `<Highlight>`: Note/warning/caution blocks (use sparingly)
+- Tabs: Multi-option content display
+- Multi-tab code blocks
+- Tags
+
+See `_partials/_formatting_examples.md` for syntax and examples.
+
+### Variables
+Documentation uses variables for product names and UI elements with syntax `$VARIABLE_NAME`. Variables don't work in:
+- Page frontmatter
+- HTML tables and tabs
+
+Internal links: use `:currentVersion:` instead of `latest` in URLs, no need for full domain `https://www.tigerdata.com/docs`.
+
+## Style Guidelines
+
+Follow [Google Developer Documentation Style Guide](https://developers.google.com/style) with exceptions:
+- Do NOT capitalize first word after a colon
+- Use code font (backticks) for UI elements instead of semi-bold
+
+### SEO Optimization
+Include at top of pages:
+- `title`: Up to 60 characters, variation of page title
+- `excerpt`: Under 200 characters, variation of intro
+
+Summarize paragraph content in first sentence. Include main keywords in meta tags, page title, first header, and intro.
+
+## Deployment
+
+### Preview Builds
+PRs from this repository automatically trigger preview builds (allow 10 minutes). Preview URLs follow pattern: `https://docs-dev.timescale.com/docs-<branch-name-with-hyphens>`
+
+Build occurs in private `timescale/web-documentation` repository using Gatsby.
+
+### Production
+Production deployment triggered by changes to appropriate branch.
+
+## Git Workflow
+
+Branch from `latest` for all changes. PRs target `latest` branch.
+
+## Important Notes
+
+- Only commit when explicitly asked by user
+- Never include secrets or sensitive information in documentation
+- Sign CLA on first PR (automated)
+- Large codebases can be excluded from indexing using `.warpindexingignore`
+