Releasesby GlyphLakebase snapshots and backup schedule APIs are generally available
The Lakebase snapshots API and backup schedule API are now generally available. Use the snapshots API to create, get, list, and delete point-in-time snapshots, and restore a snapshot by creating a new branch from it. Use the backup schedule API to read and set a root branch's automated snapshot cadences. See Snapshots .
Also shipped Oct 26, 2026Databricks in October 2026 →
Conversation logging for Conversational analytics in BigQuery is generally available
BigQuery now supports logging data agent conversations directly to a BigQuery table within the agent's project.
Looker (Google Cloud core) data lineage is generally available
Data lineage for Looker (Google Cloud core) is now generally available, providing end-to-end visibility for LookML dashboards and Conversational Analytics agents.
BigQuery Python user-defined functions support volume mounts in preview
Python user-defined functions in BigQuery now support volume mounts, allowing users to access dependency files directly from Cloud Storage.
Looker-managed Model Context Protocol (MCP) server is generally available
The Looker-managed MCP server is now generally available, allowing AI agents to interact with business data and LookML models without middleware.
BigQuery REGEXP_EXTRACT_GROUPS function is in preview
The new REGEXP_EXTRACT_GROUPS function allows users to extract substrings matching multiple capturing groups in a regular expression.
OpenAI GPT-6.1 Terra is now generally available on Amazon Bedrock
OpenAI GPT-6.1 Terra is now generally available on Amazon Bedrock, offering improved visual reasoning and computer use capabilities for enterprise workloads.
More from LakebaseEvery Lakebase release →
Lakebase Insights moves to per-project settings, with on-demand runs (Beta)
Lakebase Insights now diagnoses issues using telemetry from the system.lakebase system tables and recommends next steps. The Lakebase Insights workspace preview enables automatic telemetry capture. Users with CAN MANAGE can configure Insights directly in each project's Settings , without creating an observability configuration.
Lakebase Search supports Chinese, Japanese, and Korean full-text search
The lakebase_tokenizer extension now supports keyword search over Chinese, Japanese, and Korean (CJK) text. These languages don't separate words with spaces, so native PostgreSQL full-text search can't split them into useful search terms.
Replicate data in and out of Lakebase with Postgres logical replication
You can now use native Postgres logical replication to stream changes into and out of Lakebase. Migrate an existing Postgres database into Lakebase and keep it in sync until you cut over, or publish changes from Lakebase to external Postgres databases. See Logical replication .
LTAP Direct Writes is generally available
LTAP Direct Writes is now generally available. It speeds up how synced tables load into Lakebase by writing the initial load and full refreshes directly to the storage layer instead of through your compute endpoint, so large loads finish faster without competing with your queries.
Supported Postgres extensions updated to new versions
The following supported Postgres extensions are now available at newer versions. Existing installations keep their current version until you update them with ALTER EXTENSION .
Lakebase Search adds a configurable text tokenizer for keyword search
The new lakebase_tokenizer extension lets you control how Lakebase Search turns text into search terms, so keyword search matches the way your data and users actually read. Native PostgreSQL full-text search gives you little control over this step.
ai_search can search Lakebase synced tables (Beta)
The ai_search function can now retrieve from Lakebase synced tables with Lakebase Search enabled, in addition to AI Search indexes. Add a lakebase_search knowledge source to search a Lakebase synced table, or combine it with vector_search sources in the same call. This feature is in Beta . See ai_search function .
Lakebase observability telemetry in system tables (Beta)
Lakebase captures its Postgres observability telemetry into the system.lakebase system tables, with no configuration to create and no destination to choose. Query plans, session history, wait events, schema-change history, database and compute health, and Postgres logs land there, and records are retained for 7 days.