Merge branch 'latest' into 503-cli-mcp-agent-milestone-branch

billy-the-fish · web-flow · commit 1b3091b3e810 · 2025-10-20T09:31:28.000+02:00
diff --git a/_partials/_early_access_11_25.md b/_partials/_early_access_11_25.md
@@ -0,0 +1 @@
+<Tag variant="hollow">Early access: October 2025</Tag>
diff --git a/_partials/_integration-prereqs-cloud-only.md b/_partials/_integration-prereqs-cloud-only.md
@@ -1,7 +1,7 @@
 
 To follow the steps on this page:
 
-* Create a target [$SERVICE_LONG][create-service] with time-series and analytics enabled.
+* Create a target [$SERVICE_LONG][create-service] with the Real-time analytics capability.
 
    You need your [connection details][connection-info]. 
  
diff --git a/_partials/_integration-prereqs.md b/_partials/_integration-prereqs.md
@@ -1,6 +1,6 @@
 To follow the steps on this page:
 
-* Create a target [$SERVICE_LONG][create-service] with time-series and analytics enabled.
+* Create a target [$SERVICE_LONG][create-service] with the Real-time analytics capability.
 
    You need [your connection details][connection-info]. This procedure also 
    works for [$SELF_LONG][enable-timescaledb].
diff --git a/_partials/_timescaledb-gucs.md b/_partials/_timescaledb-gucs.md
@@ -81,4 +81,4 @@
 | `skip_scan_run_cost_multiplier` | `REAL` | `1.0` | Default is 1.0 i.e. regularly estimated SkipScan run cost, 0.0 will make SkipScan to have run cost = 0<br />min: `0.0`, max: `1.0` |
 | `telemetry_level` | `ENUM` | `TELEMETRY_DEFAULT` | Level used to determine which telemetry to send |
 
-Version: [2.22.0](https://github.com/timescale/timescaledb/releases/tag/2.22.0)
+Version: [2.22.1](https://github.com/timescale/timescaledb/releases/tag/2.22.1)
diff --git a/api/data-retention/add_retention_policy.md b/api/data-retention/add_retention_policy.md
@@ -18,55 +18,49 @@ information, see the [drop_chunks][drop_chunks] section. This implements a data
 retention policy and removes data on a schedule. Only one retention policy may
 exist per hypertable.
 
-## Samples
-
-Create a data retention policy to discard chunks greater than 6 months old:
-
-```sql
-SELECT add_retention_policy('conditions', drop_after => INTERVAL '6 months');
-```
-
-Create a data retention policy with an integer-based time column:
+When you create a retention policy on a hypertable with an integer based time column, you must set the 
+[integer_now_func][set_integer_now_func] to match your data. If you are seeing `invalid value` issues when you 
+call `add_retention_policy`, set `VERBOSITY verbose` to see the full context.
 
-```sql
-SELECT add_retention_policy('conditions', drop_after => BIGINT '600000');
-```
+## Samples
 
-Create a data retention policy to discard chunks created before 6 months:
+- **Create a data retention policy to discard chunks greater than 6 months old**:
 
-```sql
-SELECT add_retention_policy('conditions', drop_created_before => INTERVAL '6 months');
-```
+    ```sql
+    SELECT add_retention_policy('conditions', drop_after => INTERVAL '6 months');
+    ```
+    When you call `drop_after`, the time data range present in the partitioning time column is used to select the target
+    chunks.
+ 
+- **Create a data retention policy with an integer-based time column**:
 
-Note above that when `drop_after` is used then the time data range
-present in the partitioning time column is used to select the target
-chunks. Whereas, when `drop_created_before` is used then the chunks
-which were created 3 months ago are selected.
+    ```sql
+    SELECT add_retention_policy('conditions', drop_after => BIGINT '600000');
+    ```
 
-## Required arguments
+- **Create a data retention policy to discard chunks created before 6 months**:
 
-|Name|Type|Description|
-|-|-|-|
-|`relation`|REGCLASS|Name of the hypertable or continuous aggregate to create the policy for|
-|`drop_after`|INTERVAL or INTEGER|Chunks fully older than this interval when the policy is run are dropped|
-|`schedule_interval`|INTERVAL|The interval between the finish time of the last execution and the next start. Defaults to NULL.|
-|`initial_start`|TIMESTAMPTZ|Time the policy is first run. Defaults to NULL. If omitted, then the schedule interval is the interval between the finish time of the last execution and the next start. If provided, it serves as the origin with respect to which the next_start is calculated.|
-|`timezone`|TEXT|A valid time zone. If `initial_start` is also specified, subsequent executions of the retention policy are aligned on its initial start. However, daylight savings time (DST) changes may shift this alignment. Set to a valid time zone if this is an issue you want to mitigate. If omitted, UTC bucketing is performed. Defaults to `NULL`.|
+    ```sql
+    SELECT add_retention_policy('conditions', drop_created_before => INTERVAL '6 months');
+    ```
+    When you call `drop_created_before`, chunks created 3 months ago are selected.
 
-The `drop_after` parameter should be specified differently depending on the
-type of the time column of the hypertable:
+## Arguments
 
-*   For hypertables with TIMESTAMP, TIMESTAMPTZ, and DATE time columns: the time
-interval should be an INTERVAL type.
-*   For hypertables with integer-based timestamps: the time interval should be an
-integer type (this requires the [integer_now_func][set_integer_now_func] to be set).
+| Name | Type | Default | Required | Description                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|-|-|-|-|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|`relation`|REGCLASS|-|✔| Name of the hypertable or continuous aggregate to create the policy for                                                                                                                                                                                                                                                                                                                                                                         |
+|`drop_after`|INTERVAL or INTEGER|-|✔| Chunks fully older than this interval when the policy is run are dropped. <BR/> You specify `drop_after` differently depending on the hypertable time column type: <ul><li>TIMESTAMP, TIMESTAMPTZ, and DATE: use INTERVAL type</li><li>Integer-based timestamps: use INTEGER type. You must set <a href="https://docs.tigerdata.com/api/latest/hypertable/set_integer_now_func/">integer_now_func</a> to match your data</li></ul> |
+|`schedule_interval`|INTERVAL|`NULL`|✖| The interval between the finish time of the last execution and the next start.                                                                                                                                                                                                                                                                                                                                                                  |
+|`initial_start`|TIMESTAMPTZ|`NULL`|✖| Time the policy is first run. If omitted, then the schedule interval is the interval between the finish time of the last execution and the next start. If provided, it serves as the origin with respect to which the next_start is calculated.                                                                                                                                                                                                 |
+|`timezone`|TEXT|`NULL`|✖| A valid time zone. If `initial_start` is also specified, subsequent executions of the retention policy are aligned on its initial start. However, daylight savings time (DST) changes may shift this alignment. Set to a valid time zone if this is an issue you want to mitigate. If omitted, UTC bucketing is performed.                                                                                                                      |
+|`if_not_exists`|BOOLEAN|`false`|✖| Set to `true` to avoid an error if the `drop_chunks_policy` already exists. A notice is issued instead.                                                                                                                                                                                                                                                                                                                                         |
+|`drop_created_before`|INTERVAL|`NULL`|✖| Chunks with creation time older than this cut-off point are dropped. The cut-off point is computed as `now() - drop_created_before`. Not supported for continuous aggregates yet.                                                                                                                                                                                                                                                               |
 
-## Optional arguments
+You specify `drop_after` differently depending on the hypertable time column type:
 
-|Name|Type|Description|
-|-|-|-|
-|`if_not_exists`|BOOLEAN|Set to `true` to avoid an error if the `drop_chunks_policy` already exists. A notice is issued instead. Defaults to `false`.|
-|`drop_created_before`|INTERVAL|Chunks with creation time older than this cut-off point are dropped. The cut-off point is computed as `now() - drop_created_before`. Defaults to `NULL`. Not supported for continuous aggregates yet.|
+*  TIMESTAMP, TIMESTAMPTZ, and DATE time columns: the time interval should be an INTERVAL type.
+*  Integer-based timestamps: the time interval should be an integer type. You must set the [integer_now_func][set_integer_now_func].
 
 ## Returns
 
diff --git a/use-timescale/backup-restore.md b/use-timescale/backup-restore.md
@@ -60,15 +60,24 @@ You can have one cross-region backup per $SERVICE_SHORT. To change the region of
 
 <Availability products={['cloud']} />
 
-To recover your $SERVICE_SHORT from a destructive or unwanted action, create a point-in-time recovery fork. You can recover a $SERVICE_SHORT to any point within the period [defined by your pricing plan][pricing-and-account-management]. The original $SERVICE_SHORT stays untouched to avoid losing data created since the time of recovery.
+To recover your $SERVICE_SHORT from a destructive or unwanted action, create a point-in-time recovery fork. You can 
+recover a $SERVICE_SHORT to any point within the period [defined by your pricing plan][pricing-and-account-management].
+The provision time for the recovery fork is typically less than twenty minutes, but can take longer depending on the 
+amount of WAL to be replayed. The original $SERVICE_SHORT stays untouched to avoid losing data created since the time 
+of recovery.
 
-Since the point-in-time recovery is done in a fork, to migrate your
-application to the point of recovery, change the connection
-strings in your application to use the fork. The provision time for the
-recovery fork is typically less than twenty minutes, but can take longer
-depending on the amount of WAL to be replayed.
+All tiered data remains recoverable during the PITR period. When restoring to any point-in-time recovery fork, your
+$SERVICE_SHORT contains all data that existed at that moment - whether it was stored in high-performance or low-cost
+storage. 
 
-To avoid paying for compute for the recovery fork and the original $SERVICE_SHORT, pause the original to only pay storage costs.
+When you restore a recovery fork:
+- Data restored from a PITR point is placed into high-performance storage
+- The tiered data, as of that point in time, remains in tiered storage
+
+
+
+To avoid paying for compute for the recovery fork and the original $SERVICE_SHORT, pause the original to only pay 
+storage costs.
 
 You initiate a point-in-time recovery from a same-region or cross-region backup in $CONSOLE_LONG:
 
@@ -92,7 +101,11 @@ You initiate a point-in-time recovery from a same-region or cross-region backup
 1.  Confirm by clicking `Create recovery fork`.
 
     A fork of the $SERVICE_SHORT is created. The recovered $SERVICE_SHORT shows in `Services` with a label specifying which $SERVICE_SHORT it has been forked from.
-1.  Update the connection strings in your app to use the fork.
+1.  Update the connection strings in your app
+
+    Since the point-in-time recovery is done in a fork, to migrate your
+    application to the point of recovery, change the connection
+    strings in your application to use the fork.
 
 </Procedure>
 
diff --git a/use-timescale/extensions/index.md b/use-timescale/extensions/index.md
@@ -16,13 +16,14 @@ The following $PG extensions are installed with each $SERVICE_LONG:
 
 ## $COMPANY extensions
 
-| Extension                                  | Description                        | Enabled by default                                  |
-|--------------------------------------------|------------------------------------|-----------------------------------------------------|
-| [pgai][pgai]                               | Helper functions for AI workflows  | For [AI-focused][services] $SERVICE_SHORTs          |
-| [pgvector][pgvector]                       | Vector similarity search for $PG   | For [AI-focused][services] $SERVICE_SHORTs          |
-| [pgvectorscale][pgvectorscale]             | Advanced indexing for vector data  | For [AI-focused][services] $SERVICE_SHORTs          |
-| [timescaledb_toolkit][timescaledb-toolkit] | TimescaleDB Toolkit                | For [Real-time analytics][services] $SERVICE_SHORTs |
-| [timescaledb][timescaledb]                 | TimescaleDB                        | For all $SERVICE_SHORTs                             |
+| Extension                                   | Description                                | Enabled by default                                                    |
+|---------------------------------------------|--------------------------------------------|-----------------------------------------------------------------------|
+| [pgai][pgai]                                | Helper functions for AI workflows          | For [AI-focused][services] $SERVICE_SHORTs                            |
+| [pg_textsearch][pg_textsearch]              | [BM25][bm25-wiki]-based full-text search   | Currently early access. For development and staging environments only |
+| [pgvector][pgvector]                        | Vector similarity search for $PG           | For [AI-focused][services] $SERVICE_SHORTs                            |
+| [pgvectorscale][pgvectorscale]              | Advanced indexing for vector data          | For [AI-focused][services] $SERVICE_SHORTs                            |
+| [timescaledb_toolkit][timescaledb-toolkit]  | TimescaleDB Toolkit                        | For [Real-time analytics][services] $SERVICE_SHORTs                   |
+| [timescaledb][timescaledb]                  | TimescaleDB                                | For all $SERVICE_SHORTs                                               |
 
 ## $PG built-in extensions
 
@@ -138,6 +139,7 @@ The following $PG extensions are installed with each $SERVICE_LONG:
 [refint]: https://www.postgresql.org/docs/current/contrib-spi.html
 [seg]: https://www.postgresql.org/docs/current/seg.html
 [pgcrypto]: /use-timescale/:currentVersion:/extensions/pgcrypto/
+[pg_textsearch]: /use-timescale/:currentVersion:/extensions/pg-textsearch/
 [sslinfo]: https://www.postgresql.org/docs/current/sslinfo.html
 [tablefunc]: https://www.postgresql.org/docs/current/tablefunc.html
 [tcn]: https://www.postgresql.org/docs/current/tcn.html
@@ -153,3 +155,4 @@ The following $PG extensions are installed with each $SERVICE_LONG:
 [timescale-extensions]: #timescale-extensions
 [third-party]: #third-party-extensions
 [services]: /getting-started/:currentVersion:/
+[bm25-wiki]: https://en.wikipedia.org/wiki/Okapi_BM25
diff --git a/use-timescale/extensions/pg-textsearch.md b/use-timescale/extensions/pg-textsearch.md
diff --git a/use-timescale/page-index/page-index.js b/use-timescale/page-index/page-index.js

Original file line number	Diff line number	Diff line change
`@@ -0,0 +1 @@`
	`1`	`+<Tag variant="hollow">Early access: October 2025</Tag>`