> ## Documentation Index > Fetch the complete documentation index at: https://cockroachlabs.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # What's New in v26.1 export const releases = { stable: { minor: "26.2", patch: "v26.2.3" }, perMinor: { "23.2": { latest: "23.2.31", predecessor: "23.1", type: "Regular" }, "24.1": { latest: "24.1.31", predecessor: "23.2", type: "Regular" }, "24.3": { latest: "24.3.34", predecessor: "24.2", type: "Regular" }, "25.2": { latest: "25.2.20", predecessor: "25.1", type: "Regular" }, "25.4": { latest: "25.4.12", predecessor: "25.3", type: "Regular" }, "26.1": { latest: "26.1.6", predecessor: "25.4", type: "Innovation" }, "26.2": { latest: "26.2.3", predecessor: "26.1", type: "Regular" } }, patches: [{ version: "v26.2.3", minor: "26.2", date: "June 26, 2026", withdrawn: false, prerelease: false, dockerTag: "v26.2.3", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.2.2", minor: "26.2", date: "June 5, 2026", withdrawn: false, prerelease: false, dockerTag: "v26.2.2", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.2.1", minor: "26.2", date: "May 22, 2026", withdrawn: false, prerelease: false, dockerTag: "v26.2.1", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.2.0", minor: "26.2", date: "April 27, 2026", withdrawn: false, prerelease: false, dockerTag: "v26.2.0", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.2.0-rc.1", minor: "26.2", date: "April 15, 2026", withdrawn: false, prerelease: true, dockerTag: "v26.2.0-rc.1", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.2.0-beta.3", minor: "26.2", date: "April 8, 2026", withdrawn: false, prerelease: true, dockerTag: "v26.2.0-beta.3", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.2.0-beta.2", minor: "26.2", date: "April 1, 2026", withdrawn: false, prerelease: true, dockerTag: "v26.2.0-beta.2", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.2.0-beta.1", minor: "26.2", date: "March 25, 2026", withdrawn: false, prerelease: true, dockerTag: "v26.2.0-beta.1", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.2.0-alpha.2", minor: "26.2", date: "March 18, 2026", withdrawn: false, prerelease: true, dockerTag: "v26.2.0-alpha.2", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.2.0-alpha.1", minor: "26.2", date: "March 11, 2026", withdrawn: false, prerelease: true, dockerTag: "v26.2.0-alpha.1", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.1.6", minor: "26.1", date: "June 26, 2026", withdrawn: false, prerelease: false, dockerTag: "v26.1.6", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.1.5", minor: "26.1", date: "May 29, 2026", withdrawn: false, prerelease: false, dockerTag: "v26.1.5", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.1.4", minor: "26.1", date: "May 1, 2026", withdrawn: false, prerelease: false, dockerTag: "v26.1.4", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.1.3", minor: "26.1", date: "April 20, 2026", withdrawn: false, prerelease: false, dockerTag: "v26.1.3", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.1.2", minor: "26.1", date: "April 3, 2026", withdrawn: false, prerelease: false, dockerTag: "v26.1.2", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.1.1", minor: "26.1", date: "March 9, 2026", withdrawn: false, prerelease: false, dockerTag: "v26.1.1", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.1.0", minor: "26.1", date: "February 18, 2026", withdrawn: false, prerelease: false, dockerTag: "v26.1.0", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.1.0-rc.1", minor: "26.1", date: "January 22, 2026", withdrawn: false, prerelease: true, dockerTag: "v26.1.0-rc.1", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.1.0-beta.3", minor: "26.1", date: "January 14, 2026", withdrawn: false, prerelease: true, dockerTag: "v26.1.0-beta.3", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.1.0-beta.2", minor: "26.1", date: "January 7, 2026", withdrawn: false, prerelease: true, dockerTag: "v26.1.0-beta.2", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.1.0-beta.1", minor: "26.1", date: "December 17, 2025", withdrawn: false, prerelease: true, dockerTag: "v26.1.0-beta.1", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.1.0-alpha.2", minor: "26.1", date: "December 11, 2025", withdrawn: false, prerelease: true, dockerTag: "v26.1.0-alpha.2", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v26.1.0-alpha.1", minor: "26.1", date: "December 4, 2025", withdrawn: false, prerelease: true, dockerTag: "v26.1.0-alpha.1", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v25.4.12", minor: "25.4", date: "June 26, 2026", withdrawn: false, prerelease: false, dockerTag: "v25.4.12", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v25.4.11", minor: "25.4", date: "May 29, 2026", withdrawn: false, prerelease: false, dockerTag: "v25.4.11", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v25.4.10", minor: "25.4", date: "May 1, 2026", withdrawn: false, prerelease: false, dockerTag: "v25.4.10", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v25.4.9", minor: "25.4", date: "April 20, 2026", withdrawn: false, prerelease: false, dockerTag: "v25.4.9", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v25.4.8", minor: "25.4", date: "April 10, 2026", withdrawn: false, prerelease: false, dockerTag: "v25.4.8", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v25.4.7", minor: "25.4", date: "April 3, 2026", withdrawn: false, prerelease: false, dockerTag: "v25.4.7", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v25.4.6", minor: "25.4", date: "March 9, 2026", withdrawn: false, prerelease: false, dockerTag: "v25.4.6", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v25.4.5", minor: "25.4", date: "February 19, 2026", withdrawn: false, prerelease: false, dockerTag: "v25.4.5", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v25.4.4", minor: "25.4", date: "February 11, 2026", withdrawn: false, prerelease: false, dockerTag: "v25.4.4", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v25.4.3", minor: "25.4", date: "January 9, 2026", withdrawn: false, prerelease: false, dockerTag: "v25.4.3", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v25.4.2", minor: "25.4", date: "December 12, 2025", withdrawn: false, prerelease: false, dockerTag: "v25.4.2", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v25.4.1", minor: "25.4", date: "December 3, 2025", withdrawn: false, prerelease: false, dockerTag: "v25.4.1", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v25.4.0", minor: "25.4", date: "November 3, 2025", withdrawn: false, prerelease: false, dockerTag: "v25.4.0", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v25.4.0-rc.1", minor: "25.4", date: "October 22, 2025", withdrawn: false, prerelease: true, dockerTag: "v25.4.0-rc.1", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v25.4.0-beta.3", minor: "25.4", date: "October 16, 2025", withdrawn: false, prerelease: true, dockerTag: "v25.4.0-beta.3", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v25.4.0-beta.2", minor: "25.4", date: "October 10, 2025", withdrawn: false, prerelease: true, dockerTag: "v25.4.0-beta.2", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v25.4.0-beta.1", minor: "25.4", date: "October 1, 2025", withdrawn: false, prerelease: true, dockerTag: "v25.4.0-beta.1", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v25.4.0-alpha.2", minor: "25.4", date: "September 23, 2025", withdrawn: false, prerelease: true, dockerTag: "v25.4.0-alpha.2", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }, { version: "v25.4.0-alpha.1", minor: "25.4", date: "September 17, 2025", withdrawn: false, prerelease: true, dockerTag: "v25.4.0-alpha.1", platforms: ["linux-amd64", "linux-arm64", "darwin-amd64", "darwin-arm64", "windows-amd64"] }] }; export const InternalLink = ({version, path = "", children, ...props}) => { let detectedVersion = version || "stable"; if (typeof window !== 'undefined' && !version) { const match = window.location.pathname.match(/\/docs\/([^/]+)/); if (match) { detectedVersion = match[1]; } } const normalizedPath = path.startsWith("/") ? path.slice(1) : path; return {children} ; }; export const MarketoEmailForm = ({successMessage = "Thanks!"}) => { useEffect(() => { function initializeReleaseNotesSignup() { if (window.__cockroachReleaseNotesSignupInitialized) { if (window.__cockroachReleaseNotesRefresh) { window.__cockroachReleaseNotesRefresh(); } return; } window.__cockroachReleaseNotesSignupInitialized = true; const MARKETO_BASE_URL = "https://go.cockroachlabs.com"; const MARKETO_MUNCHKIN_ID = "350-QIN-827"; const MARKETO_FORMS_SCRIPT = "https://go.cockroachlabs.com/js/forms2/js/forms2.min.js"; const RELEASE_NOTES_FORM_ID = 1083; const EMAIL_ERROR = "Enter a valid email address."; const FORM_LOAD_ERROR = "Unable to load the release notes form. Disable content blockers and try again."; const LOCALHOST_ERROR = "Marketo rejects submissions from localhost. Test this form on a deployed preview URL."; const SUCCESS_MESSAGE = "Thanks!"; const WIDGET_SELECTOR = "[data-release-notes-signup]"; const FORM_MOUNT_ID = "cockroachReleaseNotesFormMount"; const SUBMIT_FRAME_NAME = "cockroachReleaseNotesSubmitFrame"; const widgetState = new WeakMap(); let marketoScriptPromise; let marketoFormPromise; let activeWidget = null; function toSecureMarketoUrl(url) { if (typeof url !== "string") { return url; } return url.replace("http://go.cockroachlabs.com", "https://go.cockroachlabs.com"); } function patchMarketoFrameTransport() { if (window.__cockroachReleaseNotesFrameTransportPatched || typeof HTMLIFrameElement === "undefined") { return; } const iframeProto = HTMLIFrameElement.prototype; const originalSetAttribute = iframeProto.setAttribute; iframeProto.setAttribute = function (name, value) { if (name === "src") { value = toSecureMarketoUrl(value); } return originalSetAttribute.call(this, name, value); }; const srcDescriptor = Object.getOwnPropertyDescriptor(iframeProto, "src"); if (srcDescriptor && typeof srcDescriptor.get === "function" && typeof srcDescriptor.set === "function") { try { Object.defineProperty(iframeProto, "src", { configurable: true, enumerable: srcDescriptor.enumerable, get: function () { return srcDescriptor.get.call(this); }, set: function (value) { srcDescriptor.set.call(this, toSecureMarketoUrl(value)); } }); } catch (error) {} } window.__cockroachReleaseNotesFrameTransportPatched = true; } function getState(widget) { let state = widgetState.get(widget); if (!state) { state = { error: "", isSubmitted: false, isSubmitting: false, successMessage: widget.getAttribute("data-success-message") || SUCCESS_MESSAGE, submitTimeoutId: null }; widgetState.set(widget, state); } return state; } function getElements(widget) { return { emailInput: widget.querySelector("[data-release-notes-email]"), error: widget.querySelector("[data-release-notes-error]"), errorText: widget.querySelector("[data-release-notes-error-text]"), submitButton: widget.querySelector("[data-release-notes-submit]"), success: widget.querySelector("[data-release-notes-success]"), successText: widget.querySelector("[data-release-notes-success-text]") }; } function ensureFormMount() { let mount = document.getElementById(FORM_MOUNT_ID); if (mount) { return mount; } mount = document.createElement("div"); mount.id = FORM_MOUNT_ID; mount.setAttribute("aria-hidden", "true"); mount.style.display = "none"; document.body.appendChild(mount); return mount; } function getDomForm(form) { const formElement = typeof form.getFormElem === "function" ? form.getFormElem() : null; return formElement && formElement[0] ? formElement[0] : formElement; } function mountMarketoForm(form) { const domForm = getDomForm(form); if (!domForm || domForm.isConnected) { return domForm; } ensureFormMount().appendChild(domForm); return domForm; } function applyFormValues(form, values) { if (typeof form.setValues === "function") { form.setValues(values); return; } if (typeof form.vals === "function") { form.vals(values); } } function ensureSubmitFrame() { let frame = document.querySelector('iframe[name="' + SUBMIT_FRAME_NAME + '"]'); if (frame) { return frame; } frame = document.createElement("iframe"); frame.name = SUBMIT_FRAME_NAME; frame.setAttribute("aria-hidden", "true"); frame.tabIndex = -1; frame.style.display = "none"; document.body.appendChild(frame); return frame; } function clearSubmitTimeout(widget) { const state = getState(widget); if (state.submitTimeoutId) { window.clearTimeout(state.submitTimeoutId); state.submitTimeoutId = null; } } function forceSecureMarketoFrame() { const frame = document.querySelector("#MktoForms2XDIframe"); if (!frame) { return; } const currentSrc = frame.getAttribute("src") || frame.src; if (!currentSrc) { return; } const secureSrc = toSecureMarketoUrl(currentSrc); if (secureSrc !== currentSrc) { frame.setAttribute("src", secureSrc); } } function ensureSecureMarketoFrame() { patchMarketoFrameTransport(); forceSecureMarketoFrame(); if (window.__cockroachReleaseNotesFrameObserverInitialized || typeof MutationObserver === "undefined") { return; } const observer = new MutationObserver(function () { forceSecureMarketoFrame(); }); observer.observe(document.documentElement, { childList: true, subtree: true, attributes: true, attributeFilter: ["src"] }); window.__cockroachReleaseNotesFrameObserverInitialized = true; window.__cockroachReleaseNotesFrameObserver = observer; } function render(widget) { if (!widget || !document.contains(widget)) { return; } const state = getState(widget); const elements = getElements(widget); if (elements.submitButton) { elements.submitButton.disabled = state.isSubmitting; } if (elements.emailInput) { elements.emailInput.setAttribute("aria-invalid", state.error ? "true" : "false"); } if (elements.error) { elements.error.hidden = !state.error; elements.error.style.display = state.error ? "block" : "none"; } if (elements.errorText) { elements.errorText.textContent = state.error; } if (elements.success) { elements.success.hidden = !state.isSubmitted; elements.success.style.display = state.isSubmitted ? "block" : "none"; } if (elements.successText) { elements.successText.textContent = state.successMessage || SUCCESS_MESSAGE; } } function hideMarketoForm(form) { const formElement = form && typeof form.getFormElem === "function" ? form.getFormElem() : null; if (!formElement) { return; } if (typeof formElement.hide === "function") { formElement.hide(); return; } if (formElement[0] && formElement[0].style) { formElement[0].style.display = "none"; return; } if (formElement.style) { formElement.style.display = "none"; } } function isValidEmail(value) { return (/^[^\s@]+@[^\s@]+\.[^\s@]+$/).test(value); } function isFormLoadError(error) { return Boolean(error && typeof error === "object" && (error.code === "marketo_load_failed" || error.code === "marketo_not_available" || error.code === "marketo_form_init_failed")); } function isLocalhost() { return window.location.hostname === "localhost" || window.location.hostname === "127.0.0.1"; } function loadMarketoForms() { ensureSecureMarketoFrame(); if (window.MktoForms2) { return Promise.resolve(window.MktoForms2); } if (!marketoScriptPromise) { marketoScriptPromise = new Promise(function (resolve, reject) { function finalizeLoad() { if (window.MktoForms2) { forceSecureMarketoFrame(); resolve(window.MktoForms2); return; } marketoScriptPromise = null; const error = new Error("MktoForms2 did not load."); error.code = "marketo_not_available"; reject(error); } function handleError() { marketoScriptPromise = null; const error = new Error("Failed to load Marketo forms."); error.code = "marketo_load_failed"; reject(error); } const existingScript = document.querySelector('script[src="' + MARKETO_FORMS_SCRIPT + '"]'); if (existingScript) { existingScript.addEventListener("load", finalizeLoad, { once: true }); existingScript.addEventListener("error", handleError, { once: true }); return; } const script = document.createElement("script"); script.src = MARKETO_FORMS_SCRIPT; script.async = true; script.addEventListener("load", finalizeLoad, { once: true }); script.addEventListener("error", handleError, { once: true }); document.body.appendChild(script); }); } return marketoScriptPromise; } function attachFormCallbacks(form) { if (form.__releaseNotesCallbacksAttached) { return; } form.__releaseNotesCallbacksAttached = true; form.onSuccess(function () { if (!activeWidget || !document.contains(activeWidget)) { return false; } const state = getState(activeWidget); clearSubmitTimeout(activeWidget); state.isSubmitting = false; state.isSubmitted = true; state.error = ""; state.successMessage = activeWidget.getAttribute("data-success-message") || SUCCESS_MESSAGE; render(activeWidget); return false; }); form.onValidate(function (isValid) { if (isValid || !activeWidget || !document.contains(activeWidget)) { return; } const state = getState(activeWidget); clearSubmitTimeout(activeWidget); state.isSubmitting = false; state.error = EMAIL_ERROR; render(activeWidget); }); } function ensureForm() { if (!marketoFormPromise) { marketoFormPromise = loadMarketoForms().then(function (MktoForms2) { const existingForm = typeof MktoForms2.getForm === "function" ? MktoForms2.getForm(RELEASE_NOTES_FORM_ID) : null; if (existingForm) { forceSecureMarketoFrame(); mountMarketoForm(existingForm); hideMarketoForm(existingForm); attachFormCallbacks(existingForm); ensureSubmitFrame(); return existingForm; } return new Promise(function (resolve, reject) { MktoForms2.loadForm(MARKETO_BASE_URL, MARKETO_MUNCHKIN_ID, RELEASE_NOTES_FORM_ID, function (form) { if (!form) { const error = new Error("Marketo form failed to initialize."); error.code = "marketo_form_init_failed"; reject(error); return; } forceSecureMarketoFrame(); mountMarketoForm(form); hideMarketoForm(form); attachFormCallbacks(form); ensureSubmitFrame(); resolve(form); }); }); }).catch(function (error) { marketoFormPromise = null; throw error; }); } return marketoFormPromise; } function handleEmailInput(target) { const widget = target.closest(WIDGET_SELECTOR); if (!widget) { return; } const state = getState(widget); if (!state.error) { return; } state.error = ""; render(widget); } function handleSubmit(button) { const widget = button.closest(WIDGET_SELECTOR); if (!widget) { return; } const state = getState(widget); const elements = getElements(widget); if (!elements.emailInput) { return; } const email = elements.emailInput.value.trim(); if (!email) { state.error = EMAIL_ERROR; render(widget); return; } state.error = ""; state.isSubmitted = false; state.isSubmitting = true; state.successMessage = widget.getAttribute("data-success-message") || SUCCESS_MESSAGE; render(widget); if (!isValidEmail(email)) { state.isSubmitting = false; state.error = EMAIL_ERROR; render(widget); return; } if (isLocalhost()) { state.isSubmitting = false; state.error = LOCALHOST_ERROR; render(widget); return; } activeWidget = widget; ensureForm().then(function (form) { const formValues = { Email: email, Send_me_product_and_feature_updates__c: "TRUE", subscriptionProductUpdates: "TRUE", optin: "TRUE" }; applyFormValues(form, formValues); if (typeof form.validate === "function" && !form.validate()) { state.isSubmitting = false; state.error = EMAIL_ERROR; render(widget); return; } clearSubmitTimeout(widget); state.submitTimeoutId = window.setTimeout(function () { state.isSubmitting = false; state.error = EMAIL_ERROR; render(widget); }, 10000); if (typeof form.submit !== "function") { throw new Error("marketo_submit_missing"); } form.submit(); }).catch(function (error) { clearSubmitTimeout(widget); state.isSubmitting = false; state.error = isFormLoadError(error) ? FORM_LOAD_ERROR : EMAIL_ERROR; render(widget); }); } document.addEventListener("click", function (event) { const submitButton = event.target.closest("[data-release-notes-submit]"); if (!submitButton) { return; } event.preventDefault(); handleSubmit(submitButton); }); document.addEventListener("input", function (event) { if (!(event.target instanceof HTMLInputElement) || !event.target.matches("[data-release-notes-email]")) { return; } handleEmailInput(event.target); }); window.__cockroachReleaseNotesRefresh = function () { ensureSecureMarketoFrame(); const widgets = document.querySelectorAll(WIDGET_SELECTOR); widgets.forEach(render); if (widgets.length > 0) { ensureForm().catch(function () {}); } }; window.__cockroachReleaseNotesRefresh(); } initializeReleaseNotesSignup(); }, []); return
; }; export const InlineImage = ({src, alt = "", height = "1.6em"}) => { return {alt}; }; export const SearchLink = ({term, children}) => { const handleClick = e => { e.preventDefault(); const searchButton = document.querySelector("button#search-bar-entry"); if (!searchButton) return; searchButton.click(); requestAnimationFrame(() => { const input = document.querySelector("input#search-input"); if (!input) return; const nativeInputValueSetter = Object.getOwnPropertyDescriptor(window.HTMLInputElement.prototype, "value")?.set; nativeInputValueSetter?.call(input, term); input.dispatchEvent(new Event("input", { bubbles: true })); input.dispatchEvent(new KeyboardEvent("keydown", { key: "Enter", bubbles: true })); }); }; return {children} ; }; CockroachDB v26.1 is an optional Innovation release. This version can be skipped for CockroachDB Advanced and self-hosted clusters. It is unavailable for CockroachDB Standard and CockroachDB Basic clusters. * For a summary of the most significant changes in v26.1, refer to [Feature highlights](#feature-highlights). * Before upgrading to CockroachDB v26.1, review the [backward-incompatible changes](#v26-1-0-backward-incompatible-changes), including [key cluster setting changes](#v26-1-0-cluster-settings) and [deprecations](#v26-1-0-deprecations); as well as newly identified [known limtiations](#v26-1-0-known-limitations). * For details about the support window for this release type, review the Release Support Policy. * For details about all supported releases, the release schedule, and licenses, refer to CockroachDB Releases Overview. * After downloading a supported CockroachDB binary, learn how to install CockroachDB or upgrade your cluster. Get future release notes emailed to you: ## v26.1.6 Release Date: June 26, 2026 ### Downloads Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.
Operating SystemArchitectureFull executableSQL-only executable
LinuxIntelcockroach-v26.1.6.linux-amd64.tgz
(SHA256)		cockroach-sql-v26.1.6.linux-amd64.tgz
(SHA256)
ARMcockroach-v26.1.6.linux-arm64.tgz
(SHA256)		cockroach-sql-v26.1.6.linux-arm64.tgz
(SHA256)
Mac
(Experimental)		Intelcockroach-v26.1.6.darwin-10.9-amd64.tgz
(SHA256)		cockroach-sql-v26.1.6.darwin-10.9-amd64.tgz
(SHA256)
ARMcockroach-v26.1.6.darwin-11.0-arm64.tgz
(SHA256)		cockroach-sql-v26.1.6.darwin-11.0-arm64.tgz
(SHA256)
Windows
(Experimental)		Intelcockroach-v26.1.6.windows-6.2-amd64.zip
(SHA256)		cockroach-sql-v26.1.6.windows-6.2-amd64.zip
(SHA256)
### Docker image [Multi-platform images](https://docs.docker.com/build/building/multi-platform) include support for both Intel and ARM. Multi-platform images do not take up additional space on your Docker host. Within the multi-platform image, both Intel and ARM images are **generally available** for production use. To download the Docker image: ```shell theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}} docker pull cockroachdb/cockroach:v26.1.6 ``` ### Security updates * Security: Fixed an issue where a tenant-scoped client certificate could bypass tenant-scope checks and gain cluster-wide RPC access if its subject distinguished name (DN) matched the configured root or node DN. ### Bug fixes * Fixed a bug where using the pgwire extended query protocol to prepare a statement after rolling back to a savepoint could cause an internal error (`read sequence number is ignored after savepoint rollback`). This bug affected client drivers that use the `Parse` message (extended protocol) instead of simple query execution. * Fixed a bug where using the pgwire extended query protocol to bind parameters (including enum types) to a prepared statement after rolling back to a savepoint could cause an internal error (`read sequence number is ignored after savepoint rollback`). * Fixed a bug where `INSERT`, `UPSERT`, and `UPDATE` statements could fail with the error `Access to crdb_internal and system is restricted` during schema changes that add an expression index, add a computed column, or change a column's type, even when the statement did not reference `crdb_internal` or `system`. This error occurred only while the schema change was in progress. * Fixed a bug where a `DELETE` or `UPDATE` that triggered a foreign key cascade could hit an internal assertion error ("execution requires all update columns have a fetch column") if a concurrent `ALTER TABLE ... ADD COLUMN` or `ALTER TABLE ... DROP COLUMN` modified the child table while the cascade was running. * Fixed a bug where `ALTER DATABASE system DROP REGION` could fail with the error `unsupported comparison: bytes to crdb_internal_region` when the `system` database was configured as multi-region. * Fixed a bug where setting `--advertise-sql-addr` to the same value across multiple SQL instances could cause changefeeds with `execution_locality` filters to fail with "no instances found matching locality filter". ## v26.1.5 Release Date: May 29, 2026 ### Downloads Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.
Operating SystemArchitectureFull executableSQL-only executable
LinuxIntelcockroach-v26.1.5.linux-amd64.tgz
(SHA256)		cockroach-sql-v26.1.5.linux-amd64.tgz
(SHA256)
ARMcockroach-v26.1.5.linux-arm64.tgz
(SHA256)		cockroach-sql-v26.1.5.linux-arm64.tgz
(SHA256)
Mac
(Experimental)		Intelcockroach-v26.1.5.darwin-10.9-amd64.tgz
(SHA256)		cockroach-sql-v26.1.5.darwin-10.9-amd64.tgz
(SHA256)
ARMcockroach-v26.1.5.darwin-11.0-arm64.tgz
(SHA256)		cockroach-sql-v26.1.5.darwin-11.0-arm64.tgz
(SHA256)
Windows
(Experimental)		Intelcockroach-v26.1.5.windows-6.2-amd64.zip
(SHA256)		cockroach-sql-v26.1.5.windows-6.2-amd64.zip
(SHA256)
### Docker image [Multi-platform images](https://docs.docker.com/build/building/multi-platform) include support for both Intel and ARM. Multi-platform images do not take up additional space on your Docker host. Within the multi-platform image, both Intel and ARM images are **generally available** for production use. To download the Docker image: ```shell theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}} docker pull cockroachdb/cockroach:v26.1.5 ``` ### Bug fixes * Fixed a rare panic that could occur when a virtual cluster entry was removed before it was fully populated by the rangefeed. * Fixed a bug where Physical Cluster Replication (PCR) reader virtual clusters could permanently fail authentication, causing all SQL connections to fail with "descriptor not found". * A long-running `BACKUP` to S3 using `AUTH=implicit` no longer fails with an `ExpiredToken` error when it races the rotation of the underlying short-lived credentials. The S3 client now retries `ExpiredToken`, `ExpiredTokenException`, and `RequestExpired` errors the same way the legacy `aws-sdk-go` v1 client did. * Fixed a rare nil pointer panic in the internal SQL executor. * The `storage.compression.cr` metric now includes blob files. ## v26.1.4 Release Date: May 1, 2026 ### Downloads Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.
Operating SystemArchitectureFull executableSQL-only executable
LinuxIntelcockroach-v26.1.4.linux-amd64.tgz
(SHA256)		cockroach-sql-v26.1.4.linux-amd64.tgz
(SHA256)
ARMcockroach-v26.1.4.linux-arm64.tgz
(SHA256)		cockroach-sql-v26.1.4.linux-arm64.tgz
(SHA256)
Mac
(Experimental)		Intelcockroach-v26.1.4.darwin-10.9-amd64.tgz
(SHA256)		cockroach-sql-v26.1.4.darwin-10.9-amd64.tgz
(SHA256)
ARMcockroach-v26.1.4.darwin-11.0-arm64.tgz
(SHA256)		cockroach-sql-v26.1.4.darwin-11.0-arm64.tgz
(SHA256)
Windows
(Experimental)		Intelcockroach-v26.1.4.windows-6.2-amd64.zip
(SHA256)		cockroach-sql-v26.1.4.windows-6.2-amd64.zip
(SHA256)
### Docker image [Multi-platform images](https://docs.docker.com/build/building/multi-platform) include support for both Intel and ARM. Multi-platform images do not take up additional space on your Docker host. Within the multi-platform image, both Intel and ARM images are **generally available** for production use. To download the Docker image: ```shell theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}} docker pull cockroachdb/cockroach:v26.1.4 ``` ### Bug fixes * Fixed a bug where the view owner's privileges on underlying tables were not checked when selecting from a view. A view would continue to work even after the owner lost access to the underlying tables. This also affects row-level security (RLS); the view invoker's RLS policies are enforced instead of the view owner's. To enforce privilege checks on underlying tables, set the `sql.auth.skip_underlying_view_privilege_checks.enabled` cluster setting to `false`. This setting defaults to `true` to prevent backward-incompatible behavior. * Fixed a bug where executing a mutation in a subquery (such as a CTE) could cause the "rows written" metrics like `sql.statements.index_rows_written.count` and `sql.statements.index_bytes_written.count` to not be incremented correctly. * Fixed a bug where CockroachDB might not have respected the table-level parameters `sql_stats_automatic_full_collection_enabled` and `sql_stats_automatic_partial_collection_enabled` and defaulted to using the corresponding cluster settings when deciding whether to perform automatic statistics collection on a table. * Fixed a bug where `IMPORT` error messages could include unredacted cloud storage credentials from the source URI. Credentials are now stripped from URIs before they appear in error messages. * Fixed a bug where transient I/O errors reading from the `AbortSpan` were misidentified as replica corruption, causing the node to crash. These errors are now returned to the caller as regular errors. * Fixed a bug where transient I/O errors (such as cloud storage network timeouts) during split or merge trigger evaluation were misidentified as replica corruption, causing the node to crash. These errors now correctly fail the operation, which is retried automatically. * Fixed a bug where DB Console Databases page privilege checks did not resolve role membership chains for `CONNECT` grants. Users who inherited `CONNECT` through role hierarchies now correctly see their authorized databases and tables. ## v26.1.3 Release Date: April 20, 2026 ### Downloads Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.
Operating SystemArchitectureFull executableSQL-only executable
LinuxIntelcockroach-v26.1.3.linux-amd64.tgz
(SHA256)		cockroach-sql-v26.1.3.linux-amd64.tgz
(SHA256)
ARMcockroach-v26.1.3.linux-arm64.tgz
(SHA256)		cockroach-sql-v26.1.3.linux-arm64.tgz
(SHA256)
Mac
(Experimental)		Intelcockroach-v26.1.3.darwin-10.9-amd64.tgz
(SHA256)		cockroach-sql-v26.1.3.darwin-10.9-amd64.tgz
(SHA256)
ARMcockroach-v26.1.3.darwin-11.0-arm64.tgz
(SHA256)		cockroach-sql-v26.1.3.darwin-11.0-arm64.tgz
(SHA256)
Windows
(Experimental)		Intelcockroach-v26.1.3.windows-6.2-amd64.zip
(SHA256)		cockroach-sql-v26.1.3.windows-6.2-amd64.zip
(SHA256)
### Docker image [Multi-platform images](https://docs.docker.com/build/building/multi-platform) include support for both Intel and ARM. Multi-platform images do not take up additional space on your Docker host. Within the multi-platform image, both Intel and ARM images are **generally available** for production use. To download the Docker image: ```shell theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}} docker pull cockroachdb/cockroach:v26.1.3 ``` ### Bug fixes * Fixed a bug where concurrent updates to a table using multiple column families during a partial index creation could result in data loss, incorrect `NULL` values, or validation failures in the resulting index. ## v26.1.2 Release Date: April 3, 2026 ### Downloads Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.
Operating SystemArchitectureFull executableSQL-only executable
LinuxIntelcockroach-v26.1.2.linux-amd64.tgz
(SHA256)		cockroach-sql-v26.1.2.linux-amd64.tgz
(SHA256)
ARMcockroach-v26.1.2.linux-arm64.tgz
(SHA256)		cockroach-sql-v26.1.2.linux-arm64.tgz
(SHA256)
Mac
(Experimental)		Intelcockroach-v26.1.2.darwin-10.9-amd64.tgz
(SHA256)		cockroach-sql-v26.1.2.darwin-10.9-amd64.tgz
(SHA256)
ARMcockroach-v26.1.2.darwin-11.0-arm64.tgz
(SHA256)		cockroach-sql-v26.1.2.darwin-11.0-arm64.tgz
(SHA256)
Windows
(Experimental)		Intelcockroach-v26.1.2.windows-6.2-amd64.zip
(SHA256)		cockroach-sql-v26.1.2.windows-6.2-amd64.zip
(SHA256)
### Docker image [Multi-platform images](https://docs.docker.com/build/building/multi-platform) include support for both Intel and ARM. Multi-platform images do not take up additional space on your Docker host. Within the multi-platform image, both Intel and ARM images are **generally available** for production use. To download the Docker image: ```shell theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}} docker pull cockroachdb/cockroach:v26.1.2 ``` ### Command-line changes * The `cockroach debug zip` command's `--include-files` and `--exclude-files` flags now support full zip path patterns. Patterns containing `/` are matched against the full path within the zip archive (e.g., `--include-files='debug/nodes/1/*.json'`). Patterns without `/` continue to match the base file name as before. ### Bug fixes * Fixed a bug where contention events reported the wrong key. Previously, the key field in contention events showed the transaction's anchor key (used for record placement) rather than the actual key where the conflict occurred. This made it difficult to diagnose contention issues accurately. * Fixed a bug where `CREATE INDEX` on a table with `PARTITION ALL BY` would fail if the partition columns were explicitly included in the primary key definition. * Fixed a bug that prevented the `optimizer_min_row_count` setting from applying to anti-join expressions, which could lead to bad query plans. The fix is gated behind `optimizer_use_min_row_count_anti_join_fix`, which is on by default on v26.2 and later, and off by default in earlier versions. * Fixed a bug where CockroachDB did not always promptly respond to the statement timeout when performing a hash join with an `ON` filter that is mostly `false`. * Fixed a bug introduced in v25.4 where setting `min_checkpoint_frequency` to `0` prevented changefeeds from advancing their resolved timestamp (high-water mark) and emitting resolved messages. Note that setting `min_checkpoint_frequency` lower than `500ms` is not recommended as it may cause degraded changefeed performance. * Lowered the default value of the `changefeed.max_retry_backoff` cluster setting from `10m` to `30s` to reduce changefeed lag during rolling restarts. * Fixed a rare race condition where `SHOW CREATE TABLE` could fail with a `"relation does not exist"` error if a table referenced by a foreign key was being concurrently dropped. * Fixed a bug that could cause row sampling for table statistics to crash a node due to a data race when processing a collated string column with values larger than 400 bytes. This bug has existed since before v23.1. * Fixed a bug in the legacy schema changer where rolling back a `CREATE TABLE` with inline `FOREIGN KEY` constraints could leave orphaned foreign key back-references on the referenced table, causing descriptor validation errors. * Fixed a bug where restoring a database backup containing default privileges that referenced non-existent users would leave dangling user references in the restored database descriptor. ## v26.1.1 Release Date: March 9, 2026 ### Downloads This version is currently available only for select CockroachDB Cloud clusters. To request to upgrade a CockroachDB self-hosted cluster to this version, [contact support](https://support.cockroachlabs.com/hc/requests/new). ### General changes * Added support for the `partition_alg` changefeed option to specify a Kafka partitioning algorithm. Supported values are `fnv-1a` (default) and `murmur2`. For example: `CREATE CHANGEFEED... INTO 'kafka://...' WITH partition_alg='murmur2';`. This option is only valid for Kafka v2 sinks and is controlled by the cluster setting `changefeed.partition_alg.enabled`. Once a changefeed is created with a specific algorithm, it continues to use that algorithm even if the cluster setting is later disabled, unless the changefeed is altered to use a different `partition_alg` value. ### SQL language changes * The `information_schema.crdb_datums_to_bytes` built-in function is now documented. ### Bug fixes * Fixed a bug where AVRO file imports of data with JSON or binary records could hang indefinitely when encountering stream errors from cloud storage (such as `HTTP/2` `CANCEL` errors). Import jobs will now properly fail with an error instead of hanging. * Fixed a bug which prevented successfully injecting hints using `information_schema.crdb_rewrite_inline_hints` for `INSERT`, `UPSERT`, `UPDATE`, and `DELETE` statements. This bug was present since hint injection was first introduced in v26.1.0. * Fixed a bug introduced in v26.1.0-beta.1 in which row-level TTL jobs could encounter GC threshold errors if each node had a large number of spans to process. * Fixed a bug where multi-statement explicit transactions that use `SAVEPOINT` to recover from certain errors (like duplicate key value violations) could lose writes performed before the savepoint was created in rare cases when buffered writes were enabled. Buffered writes are a public preview feature that is off by default. This bug was introduced in v25.2. * Fixed a bug that could cause changefeeds using Kafka v1 sinks to hang when the changefeed was cancelled. * Fixed a bug where queries using a generic plan with a lookup join on an index containing identity computed columns would fail with the error "cannot map variable %d to an indexed var". * Fixed an internal error "could not find format code for column N" that occurred when executing `EXPLAIN ANALYZE EXECUTE` statements via JDBC or other clients using the PostgreSQL binary protocol. * Fixed a bug where CockroachDB would encounter an internal error when evaluating builtin functions with `'{}'` as an argument without explicit type casts (e.g., `SELECT cardinality('{}');` ). A regular error is now returned instead, matching PostgreSQL behavior. * Fixed a bug in which PL/pgSQL UDFs with many IF statements would cause a timeout and/or OOM when executed from a prepared statement. This bug was introduced in versions v23.2.22, v24.1.15, v24.3.9, v25.1.2, and v25.2.0. * Fixed a bug where generating a debug zip could trigger an out-of-memory (OOM) condition on a node if malformed log entries were present in logs using `json` or `json-compact` formatting. This bug was introduced in v24.1. * Fixed a rare data race during parallel constraint checks where a fresh descriptor collection could resolve a stale enum type version. This bug was introduced in v26.1.0. ### Performance improvements * Improved changefeed checkpointing performance when changefeeds are lagging. Previously, checkpoint updates could be redundantly applied multiple times per checkpoint operation. ## v26.1.0 Release Date: February 18, 2026 With the release of CockroachDB v26.1, we've added new capabilities to help you migrate, build, and operate more efficiently. For a summary of the most significant changes, refer to [Feature Highlights](#v26-1-0-feature-highlights), which contains the following categories: * [SQL](#v26-1-0-sql) * [Security](#v26-1-0-security) * [Observability](#v26-1-0-observability) * [CockroachDB Cloud](#v26-1-0-cloud) Before upgrading to CockroachDB v26.1, be sure to also review the following [Upgrade Details](#v26-1-0-upgrade-details): * [Backward-incompatible changes](#v26-1-0-backward-incompatible-changes) * [Features that require upgrade finalization](#v26-1-0-features-that-require-upgrade-finalization) * [Key cluster setting changes](#v26-1-0-key-cluster-setting-changes) * [Deprecations](#v26-1-0-deprecations) * [Known limitations](#v26-1-0-known-limitations) ### Downloads Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.
Operating SystemArchitectureFull executableSQL-only executable
LinuxIntelcockroach-v26.1.0.linux-amd64.tgz
(SHA256)		cockroach-sql-v26.1.0.linux-amd64.tgz
(SHA256)
ARMcockroach-v26.1.0.linux-arm64.tgz
(SHA256)		cockroach-sql-v26.1.0.linux-arm64.tgz
(SHA256)
Mac
(Experimental)		Intelcockroach-v26.1.0.darwin-10.9-amd64.tgz
(SHA256)		cockroach-sql-v26.1.0.darwin-10.9-amd64.tgz
(SHA256)
ARMcockroach-v26.1.0.darwin-11.0-arm64.tgz
(SHA256)		cockroach-sql-v26.1.0.darwin-11.0-arm64.tgz
(SHA256)
Windows
(Experimental)		Intelcockroach-v26.1.0.windows-6.2-amd64.zip
(SHA256)		cockroach-sql-v26.1.0.windows-6.2-amd64.zip
(SHA256)
### Docker image [Multi-platform images](https://docs.docker.com/build/building/multi-platform) include support for both Intel and ARM. Multi-platform images do not take up additional space on your Docker host. Within the multi-platform image, both Intel and ARM images are **generally available** for production use. To download the Docker image: ```shell theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}} docker pull cockroachdb/cockroach:v26.1.0 ``` ### Feature Highlights This section summarizes the most significant user-facing changes in v26.1.0 and other features recently made available to CockroachDB users across versions. For a complete list of features and changes in v26.1, including bug fixes and performance improvements, refer to the release notes for v26.1 testing releases. You can also search the docs for sections labeled New in v26.1. #### SQL
FeatureAvailability
Ver.Self-hostedAdvancedStandardBasic
Remove read replicas from multi-region databases

Users can now set num\_replicas equal to num\_voters to remove read replicas while maintaining the required number of voting replicas for their database's survival goal. This allows reducing storage costs without compromising availability guarantees.		26.1
Custom data transforms during replication phase of a Migration

Users can now customize MOLT Replicator live replication with TypeScript userscripts to transform, filter, and control how rows are written to the target.		26.1
#### Security
FeatureAvailability
Ver.Self-hostedAdvancedStandardBasic
FIPS 140-3 Readiness (Preview)

CockroachDB v26.1 initiates FIPS 140-3 readiness by introducing the Go 1.25 native FIPS cryptographic module, replacing OpenSSL for better performance and simpler, kernel-independent deployment. This prepares CockroachDB for the upcoming transition of FIPS 140-2 to Historical status in September 2026. In v26.1, FIPS-ready deployments are in Preview for non-production testing. The final, validation-ready architecture will be available in v26.2, returning the feature to GA status and providing continuous FIPS support for customers who were running v25.4. Production FIPS-ready clusters should continue using v25.4 until v26.2 is released, and then upgrade directly to v26.2.		26.1
Disable the Root User (Preview)

To enforce security best practices, the root user account can now be disabled.		26.1
Export debug data without the Root User (Preview)

To enforce security best practices, you can now securely collect debug zip troubleshooting data without the need for the root user.		26.1
JIT Provisioning for SSO (Preview)

Users authenticating via OIDC can now be provisioned automatically upon first login, removing the need for manual account creation. Automatic provisioning has also been available with JWT authentication.		26.1
#### Observability
FeatureAvailability
Ver.Self-hostedAdvancedStandardBasic
Cloud Logging Enhancements — Changefeed Logs & Additional Cluster Context

Standardizes and enriches CockroachDB cloud logs with cluster-level context (cloud cluster ID and friendly name) and adds dedicated CHANGEFEED logging channel.		All\*
Per-Statement Statistics for UDFs & Stored Procedures

Captures execution statistics and logical plans for statements executed inside user-defined functions and stored procedures, and surfaces them in the Consoles. Teams can now see per-statement timings and resource consumption, and correlate inner statements with their parent CALL, enabling accurate performance tuning and root-cause analysis of complex, stored-procedure driven workloads.		26.1
Better Utilization & Wait-Time Accountability (Resource Attribution)

Adds KV-level CPU time and admission control wait times to statement statistics, providing direct attribution of low-level resource consumption and wait time to individual statements.		26.1
Essential & Support Metrics Tsdump — Non-Verbose Mode

Introduces a lightweight, non-verbose tsdump mode that emits only essential and support-tagged metrics, and supports inclusion of a static metric list or regex file.		26.1
#### CockroachDB Cloud
FeatureAvailability
Ver.Self-hostedAdvancedStandardBasic
Delay automatic patch upgrades by 30, 60, or 90 days

CockroachDB Cloud now gives you more control over when your clusters receive automatic patch upgrades. With the new Version Deferral feature, you can configure clusters to wait 30, 60, or 90 days after a patch is released before automatically upgrading—giving your team time to validate changes in test environments and coordinate upgrades with your application release cycles.		All\*
New Billing Viewer Role

Introduced a Billing Viewer role that grants read-only access to invoices and payment data, without permission to edit billing settings.		All\*
Feature detail key
★Features marked "All\*" were recently made available in the CockroachDB Cloud platform. They are available for all supported versions of CockroachDB, under the deployment methods specified in their row under Availability.
★★Features marked "All\*\*" were recently made available via tools maintained outside of the CockroachDB binary. They are available to use with all supported versions of CockroachDB, under the deployment methods specified in their row under Availability.
Feature is available for this deployment method of CockroachDB as specified in the icon’s column: CockroachDB Self-hosted, CockroachDB Advanced, CockroachDB Standard, or CockroachDB Basic.
Feature is not available for this deployment method of CockroachDB as specified in the icon’s column: CockroachDB Self-hosted, CockroachDB Advanced, CockroachDB Standard, or CockroachDB Basic.
### Upgrade Details Before you upgrade, review these changes and other information about the new major version. #### Backward-incompatible changes * Access to the `system` database and `crdb_internal` schema is now restricted by default. Queries to most of these namespaces will fail unless explicitly overridden via the `allow_unsafe_internals` session variable. This change prevents accidental misuse of internal-only objects that were not designed for stable external use and could lead to difficult recovery scenarios. As part of this effort, several commonly used introspection capabilities have been migrated to stable information\_schema tables: * `information_schema.crdb_datums_to_bytes` - previously only available as `crdb_internal.datums_to_bytes` * `information_schema.crdb_index_usage_stats` - previously only available as `crdb_internal.index_usage_stats` * `information_schema.crdb_rewrite_inline_hints` - replaces the function previously introduced as `crdb_internal.inject_hint` \#158085 * FIPS-ready deployments in v26.1 are in Preview and are recommended for testing and evaluation only. CockroachDB v26.1 introduces a new FIPS architecture using Go's native FIPS 140-3 cryptographic module, replacing the OpenSSL-based approach from v25.4. This architectural change means: * **Production FIPS-ready clusters should stay on v25.4** or wait to upgrade directly to v26.2, which will return FIPS support to GA status, using a version of the Go module that is in review for FIPS 140-3 validation. * **Password length requirement:** FIPS 140-3 requires a minimum password length of 14 characters. Users with passwords shorter than 14 characters may be unable to log in after upgrading to a FIPS-ready binary. For detailed upgrade guidance and migration paths, refer to FIPS-ready CockroachDB. #### Features that require upgrade finalization During a major-version upgrade, certain features and performance improvements are not available until the upgrade is finalized. In v26.1, these are: * **Improved introspection query performance**: Queries against `pg_catalog` and `information_schema` now use cached descriptors, significantly improving performance when there are many tables in the cluster. The `sql.catalog.allow_leased_descriptors.enabled` cluster setting controls this behavior (default: `true` ). For more information, see the release notes for [v26.1.0-alpha.1](#v26-1-0-alpha-1-leased-descriptors) and [v26.1.0-beta.3](#v26-1-0-beta-3-leased-descriptors-default). #### Key cluster setting changes Changes to cluster settings should be reviewed prior to upgrading. New default cluster setting values will be used unless you have manually set a value for a setting. This can be confirmed by running the SQL statement `SELECT * FROM system.settings` to view the non-default settings. ##### New cluster settings * `changefeed.default_range_distribution_strategy` supports values `default` or `balanced_simple`. This new per-changefeed setting overrides the cluster setting `changefeed.default_range_distribution_strategy` where both exist. Example: ```sql theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}} CREATE CHANGEFEED FOR x into 'null://' WITH range_distribution_strategy='balanced_simple'; ``` ##### Settings with changed defaults * `log.channel_compatibility_mode.enabled` has had its default changed to `false` * Events related to changefeed operations are now routed to the CHANGEFEED channel, while sampled queries and transactions, along with certain SQL performance events, are logged to SQL\_EXEC. To continue using the previous logging channels, set `log.channel_compatibility_mode.enabled` to `true`. * `sql.catalog.allow_leased_descriptors.enabled` (default: `true`) * Changed the default value of the `sql.catalog.allow_leased_descriptors.enabled` cluster setting to `true`. This setting allows introspection tables like `information_schema` and `pg_catalog` to use cached descriptors when building the table results, which improves the performance of introspection queries when there are many tables in the cluster. #### Deprecations The following deprecations are announced in v26.1. * **`EXPERIMENTAL SCRUB` command**: The `EXPERIMENTAL SCRUB` command is deprecated in v26.1. Use the `INSPECT` command for data consistency validation. `INSPECT` is now implemented as a generally available (GA) feature with the release of v26.1.0. * To validate data consistency, use `INSPECT` instead of `EXPERIMENTAL SCRUB` * `INSPECT` supports a `DETACHED` option to run the operation without waiting for it * For more information, see the `INSPECT` documentation * **`enable_inspect_command` session variable**: The `enable_inspect_command` session variable has been deprecated and is now effectively always set to `true`. Since `INSPECT` is now a GA feature, this session variable is no longer needed. If you have this variable set in your application configurations, you can safely remove it. #### Known limitations There are no newly identified limitations in CockroachDB v26.1. This section will be updated if functionality is later classified as a Known Limitation. ## v26.1.0-rc.1 Release Date: January 22, 2026 ### Downloads CockroachDB v26.1.0-rc.1 is a testing release. Testing releases are intended for testing and experimentation only, and are not qualified for production environments and not eligible for support or uptime SLA commitments. Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.
Operating SystemArchitectureFull executableSQL-only executable
LinuxIntelcockroach-v26.1.0-rc.1.linux-amd64.tgz
(SHA256)		cockroach-sql-v26.1.0-rc.1.linux-amd64.tgz
(SHA256)
ARMcockroach-v26.1.0-rc.1.linux-arm64.tgz
(SHA256)		cockroach-sql-v26.1.0-rc.1.linux-arm64.tgz
(SHA256)
Mac
(Experimental)		Intelcockroach-v26.1.0-rc.1.darwin-10.9-amd64.tgz
(SHA256)		cockroach-sql-v26.1.0-rc.1.darwin-10.9-amd64.tgz
(SHA256)
ARMcockroach-v26.1.0-rc.1.darwin-11.0-arm64.tgz
(SHA256)		cockroach-sql-v26.1.0-rc.1.darwin-11.0-arm64.tgz
(SHA256)
Windows
(Experimental)		Intelcockroach-v26.1.0-rc.1.windows-6.2-amd64.zip
(SHA256)		cockroach-sql-v26.1.0-rc.1.windows-6.2-amd64.zip
(SHA256)
### Docker image [Multi-platform images](https://docs.docker.com/build/building/multi-platform) include support for both Intel and ARM. Multi-platform images do not take up additional space on your Docker host. Within the multi-platform image, both Intel and ARM images are **generally available** for production use. To download the Docker image: ```shell theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}} docker pull cockroachdb/cockroach:v26.1.0-rc.1 ``` ### SQL language changes * Added support for `SHOW STATEMENT HINTS`, which displays information about the statement hints (if any) associated with the given statement fingerprint string. The fingerprint is normalized in the same way as `EXPLAIN (FINGERPRINT)` before hints are matched. Example usage: `SHOW STATEMENT HINTS FOR ' SELECT * FROM xy WHERE x = 10 '` or `SHOW STATEMENT HINTS FOR $$ SELECT * FROM xy WHERE x = 10 $$ WITH DETAILS`. * Calling `information_schema.crdb_rewrite_inline_hints` now requires the REPAIRCLUSTER privilege. * Renamed the builtin function `crdb_internal.inject_hint` (introduced in v26.1.0-alpha.2) to `information_schema.crdb_rewrite_inline_hints`. ### Operational changes * Changed goroutine profile dumps from human-readable `.txt.gz` files to binary proto `.pb.gz` files. This improves the performance of the goroutine dumper by eliminating brief in-process pauses that occurred when collecting goroutine stacks. * Added a new structured event of type `rewrite_inline_hints` that is emitted when an inline-hints rewrite rule is added using `information_schema.crdb_rewrite_inline_hints`. This event is written to both the event log and the OPS channel. * Added a new metric `sql.query.with_statement_hints.count` that is incremented whenever a statement is executed with one or more external statement hints applied. An example of an external statement hint is an inline-hints rewrite rule added by calling `information_schema.crdb_rewrite_inline_hints`. ### DB Console changes * The **SQL Activity** > **Sessions** page now defaults the **Session Status** filter to **Active, Idle** to exclude closed sessions. * Changed the unit of measurement for admission control duration metrics from microseconds to nanoseconds. The following metrics are affected: `admission.granter.slots_exhausted_duration.kv`, `admission.granter.cpu_load_short_period_duration.kv`, `admission.granter.cpu_load_long_period_duration.kv`, `admission.granter.io_tokens_exhausted_duration.kv`, `admission.granter.elastic_io_tokens_exhausted_duration.kv`, and `admission.elastic_cpu.nanos_exhausted_duration`. Note that dashboards displaying these metrics will show a discontinuity at upgrade time, with pre-upgrade values appearing much lower due to the unit change. ### Bug fixes * Fixed a bug that caused `SHOW CREATE FUNCTION` to error when the function body contained casts from columns to user-defined types. * Fixed a bug where the `pprof` UI endpoints for allocs, heap, block, and mutex profiles ignored the seconds parameter and returned immediate snapshots instead of delta profiles. * Fixed a bug where schema changes adding a `NOT NULL` constraint could enter an infinite retry loop if a row violated the constraint and contained certain content (e.g., `"EOF"` ). Such errors are now correctly classified and don't cause retries. * Fixed a bug in which inline-hints rewrite rules created with `information_schema.crdb_rewrite_inline_hints` were not correctly applied to statements run with `EXPLAIN ANALYZE`. This bug was introduced in v26.1.0-alpha.2. * Fixed a bug where IMPORT with AVRO data using OCF format could silently lose data if the underlying storage (e.g., S3) returned an error during read. Such errors are now properly reported. Other formats (specified via `data_as_binary_records` and `data_as_json_records` options) are unaffected. The bug has been present since about v20.1. ## v26.1.0-beta.3 Release Date: January 14, 2025 ### Downloads CockroachDB v26.1.0-beta.3 is a testing release. Testing releases are intended for testing and experimentation only, and are not qualified for production environments and not eligible for support or uptime SLA commitments. Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.
Operating SystemArchitectureFull executableSQL-only executable
LinuxIntelcockroach-v26.1.0-beta.3.linux-amd64.tgz
(SHA256)		cockroach-sql-v26.1.0-beta.3.linux-amd64.tgz
(SHA256)
ARMcockroach-v26.1.0-beta.3.linux-arm64.tgz
(SHA256)		cockroach-sql-v26.1.0-beta.3.linux-arm64.tgz
(SHA256)
Mac
(Experimental)		Intelcockroach-v26.1.0-beta.3.darwin-10.9-amd64.tgz
(SHA256)		cockroach-sql-v26.1.0-beta.3.darwin-10.9-amd64.tgz
(SHA256)
ARMcockroach-v26.1.0-beta.3.darwin-11.0-arm64.tgz
(SHA256)		cockroach-sql-v26.1.0-beta.3.darwin-11.0-arm64.tgz
(SHA256)
Windows
(Experimental)		Intelcockroach-v26.1.0-beta.3.windows-6.2-amd64.zip
(SHA256)		cockroach-sql-v26.1.0-beta.3.windows-6.2-amd64.zip
(SHA256)
### Docker image [Multi-platform images](https://docs.docker.com/build/building/multi-platform) include support for both Intel and ARM. Multi-platform images do not take up additional space on your Docker host. Within the multi-platform image, both Intel and ARM images are **generally available** for production use. To download the Docker image: ```shell theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}} docker pull cockroachdb/cockroach:v26.1.0-beta.3 ``` ### Enterprise edition changes * Added a new cluster setting, `security.provisioning.oidc.enabled`, to allow automatic provisioning of users when they log in for the first time via OIDC. When enabled, a new user will be created in CockroachDB upon their first successful OIDC authentication. This feature is disabled by default. ### SQL language changes * Changed the default value of the `sql.catalog.allow_leased_descriptors.enabled` cluster setting to `true`. This setting allows introspection tables like `information_schema` and `pg_catalog` to use cached descriptors when building the table results, which improves the performance of introspection queries when there are many tables in the cluster. - Added cluster settings to control the number of concurrent automatic statistics collection jobs: - `sql.stats.automatic_full_concurrency_limit` controls the maximum number of concurrent full statistics collections. The default is 1. - `sql.stats.automatic_extremes_concurrency_limit` controls the maximum number of concurrent partial statistics collections using extremes. The default is 128. Note that at most one statistics collection job can run on a single table at a time. ### Operational changes * The `kv.range_split.load_sample_reset_duration` cluster setting now defaults to `30m`. This should improve load-based splitting in rare edge cases. ### Bug fixes * Fixed an issue where long-running transactions with many statements could cause unbounded memory growth in the SQL statistics subsystem. When a transaction includes a large number of statements, the SQL statistics ingester now automatically flushes buffered statistics before the transaction commits. As a side effect, the flushed statement statistics might not have an associated transaction fingerprint ID because the transaction has not yet completed. In such cases, the transaction fingerprint ID cannot be backfilled after the fact. * Fixed a bug where a query predicate could be ignored when all of the following conditions were met: the query used a lookup join to an index, the predicate constrained a column to multiple values (e.g., `column IN (1, 2)` ), and the constrained column followed one or more columns with optional multi-value constraints in the index. This bug was introduced in v24.3.0. * Fixed a deadlock that could occur when a statistics creation task panicked. * Fixed a bug where rolling back a transaction that had just rolled back a savepoint would block other transactions accessing the same rows for five seconds. * Fixed a bug where CockroachDB could crash when handling decimals with negative scales via the extended PGWire protocol. An error is now returned instead, matching PostgreSQL behavior. * v26.1.0-beta.1 and v26.1.0-beta.2 versions of CockroachDB could encounter a rare process crash when running TTL jobs, and this has now been fixed. ### Performance improvements * Fixed a performance regression in `pg_catalog.pg_roles` and `pg_catalog.pg_authid` by avoiding privilege lookups for each row in the table. * Added a new session variable, `distsql_prevent_partitioning_soft_limited_scans`, which defaults to true. When enabled, this prevents scans with soft limits from being planned as multiple TableReaders, which decreases the initial setup costs of some fully-distributed query plans. ### Miscellaneous * Fixed a bug where import rollback could incorrectly revert data in a table that was already online. This could only occur if an import job was cancelled or failed after the import had already succeeded and the table was made available for use. ## v26.1.0-beta.2 Release Date: January 7, 2026 ### Downloads CockroachDB v26.1.0-beta.2 is a testing release. Testing releases are intended for testing and experimentation only, and are not qualified for production environments and not eligible for support or uptime SLA commitments. Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.
Operating SystemArchitectureFull executableSQL-only executable
LinuxIntelcockroach-v26.1.0-beta.2.linux-amd64.tgz
(SHA256)		cockroach-sql-v26.1.0-beta.2.linux-amd64.tgz
(SHA256)
ARMcockroach-v26.1.0-beta.2.linux-arm64.tgz
(SHA256)		cockroach-sql-v26.1.0-beta.2.linux-arm64.tgz
(SHA256)
Mac
(Experimental)		Intelcockroach-v26.1.0-beta.2.darwin-10.9-amd64.tgz
(SHA256)		cockroach-sql-v26.1.0-beta.2.darwin-10.9-amd64.tgz
(SHA256)
ARMcockroach-v26.1.0-beta.2.darwin-11.0-arm64.tgz
(SHA256)		cockroach-sql-v26.1.0-beta.2.darwin-11.0-arm64.tgz
(SHA256)
Windows
(Experimental)		Intelcockroach-v26.1.0-beta.2.windows-6.2-amd64.zip
(SHA256)		cockroach-sql-v26.1.0-beta.2.windows-6.2-amd64.zip
(SHA256)
### Docker image [Multi-platform images](https://docs.docker.com/build/building/multi-platform) include support for both Intel and ARM. Multi-platform images do not take up additional space on your Docker host. Within the multi-platform image, both Intel and ARM images are **generally available** for production use. To download the Docker image: ```shell theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}} docker pull cockroachdb/cockroach:v26.1.0-beta.2 ``` ### SQL language changes * Removed a `database_name` column from the output of `SHOW CHANGEFEED JOBS` that was added in v26.1 development, but will not be needed for v26.1 features. * Fixed a bug where creating a routine could create unnecessary column dependencies when the routine references columns through CHECK constraints (including those for RLS policies and hash-sharded indexes) or partial index predicates. These unnecessary dependencies prevented dropping the column without first dropping the routine. The fix is gated behind the session setting `use_improved_routine_deps_triggers_and_computed_cols`, which is off by default before v26.1. * `INSPECT` is now implemented as a generally available (GA) feature with the release of v26.1.0. The `enable_inspect_command` session variable has been deprecated, and is now effectively always set to `true`. ### Bug fixes * Fixed a bug that could cause prepared statements to fail with the error message "non-const expression" when they contained filters with stable functions. This bug has been present since v26.1.0-beta.2. * Fixed a bug where comments associated with constraints were left behind after the column and constraint were dropped. * Fixed a race condition where queries run after revoking `BYPASSRLS` could return wrong results because cached plans failed to notice the change immediately. * Fixed a bug where `TRUNCATE` did not behave correctly with respect to the `schema_locked` storage parameter, and was not being blocked when Logical Data Replication (LDR) was in use. This behavior was incorrect and has been fixed. * Fixed a race condition that could occur during context cancellation of an incoming snapshot. * Fixed a bug that could cause a panic during changefeed startup if an error occurred while initializing the metrics controller. * Fixed a memory accounting issue that could occur when a lease expired due to a SQL liveness session-based timeout. ### Performance improvements * Various background tasks and jobs now more actively yield to foreground work when that work is waiting to run. ## v26.1.0-beta.1 Release Date: December 17, 2025 ### Downloads CockroachDB v26.1.0-beta.1 is a testing release. Testing releases are intended for testing and experimentation only, and are not qualified for production environments and not eligible for support or uptime SLA commitments. Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.
Operating SystemArchitectureFull executableSQL-only executable
LinuxIntelcockroach-v26.1.0-beta.1.linux-amd64.tgz
(SHA256)		cockroach-sql-v26.1.0-beta.1.linux-amd64.tgz
(SHA256)
ARMcockroach-v26.1.0-beta.1.linux-arm64.tgz
(SHA256)		cockroach-sql-v26.1.0-beta.1.linux-arm64.tgz
(SHA256)
Mac
(Experimental)		Intelcockroach-v26.1.0-beta.1.darwin-10.9-amd64.tgz
(SHA256)		cockroach-sql-v26.1.0-beta.1.darwin-10.9-amd64.tgz
(SHA256)
ARMcockroach-v26.1.0-beta.1.darwin-11.0-arm64.tgz
(SHA256)		cockroach-sql-v26.1.0-beta.1.darwin-11.0-arm64.tgz
(SHA256)
Windows
(Experimental)		Intelcockroach-v26.1.0-beta.1.windows-6.2-amd64.zip
(SHA256)		cockroach-sql-v26.1.0-beta.1.windows-6.2-amd64.zip
(SHA256)
### Docker image [Multi-platform images](https://docs.docker.com/build/building/multi-platform) include support for both Intel and ARM. Multi-platform images do not take up additional space on your Docker host. Within the multi-platform image, both Intel and ARM images are **generally available** for production use. To download the Docker image: ```shell theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}} docker pull cockroachdb/cockroach:v26.1.0-beta.1 ``` ### Security updates * A new flag on the `cockroach start` command enables a `debug_user` with preconfigured access to authenticate for SQL and RPC connections. This is part of a Private Preview and disabled by default, preventing such authentication. It is intended only for debugging and troubleshooting when using the Private Preview feature that allows restricting `root` from login via SQL and RPC connections, while using `debug_user` to access debug details that would have required `root`. ### Enterprise edition changes * Improved the description of the `changefeed.default_range_distribution_strategy` cluster setting to better explain the available options and their behavior. ### SQL language changes * `crdb_internal.datums_to_bytes` is now available in the `information_schema` system catalog as `information_schema.crdb_datums_to_bytes`. * The `ALTER COLUMN...` sequence identity commands are run by the declarative schema changer. * Added support for `EXECUTE SCHEDULE {schedule_id}` to allow immediate execution of a scheduled job. This does not apply to `ALTER BACKUP SCHEDULE`; attempting to execute a backup schedule will result in an error. * `CREATE TYPE` with composite type syntax now supports array types in field definitions. For example, `CREATE TYPE t AS (a INT[])` and `CREATE TYPE t AS (a INT ARRAY)` now work correctly, matching PostgreSQL behavior. * Added the `STRICT` option for locality-aware backups. When enabled, backups fail if data from a KV node with one locality tag would be backed up to a bucket with a different locality tag, ensuring data domiciling compliance. * The `WITH RESOLVED TIMESTAMP` option can be passed to `SHOW JOBS` or `SHOW JOB` to include the resolved timestamp, if any, for the jobs in the output columns. ### Command-line changes * You can now specify a user-defined database user when generating `debug zip` and `debug tsdump` files. Use the `--user` and `--url` flags to set the username. Previously, these operations required the root user. This change provides backward compatibility by defaulting the username to `root`. This update is part of an ongoing effort to limit root user access. ### Bug fixes * Fixed a bug where modifying a scheduled backup without changing the schedule could cause the next incremental backup to be skipped. * Fixed a bug that allowed columns to be dropped despite being referenced by a routine. This could occur when a column was only referenced as a target column in the SET clause of an UPDATE statement within the routine. This fix only applies to newly-created routines. In versions prior to v26.1, the fix must be enabled by setting the session variable `prevent_update_set_column_drop`. * Fixed a bug that caused newly-created routines to incorrectly prevent dropping columns that were not directly referenced, most notably columns referenced by computed column expressions. The fix is gated behind the session setting `use_improved_routine_deps_triggers_and_computed_cols`, which is off by default prior to v26.1. * Fixed a bug that could cause incorrect query results when using prepared statements with NULL placeholders. The bug has existed since v21.2 and violated SQL NULL-equality semantics by returning rows with NULL values when the result set should have been empty. From v21.2 to v25.3, the bug occurred when all of the following were true: * The query was run with an explicit or implicit prepared statement * The query had an equality filter on a placeholder and a UNIQUE column * The column contained NULL values * The placeholder was assigned to NULL during execution Starting in v25.4, the requirements were loosened: the column no longer needed to be UNIQUE, and the bug could reproduce if the column was included in any index. * Fixed a bug where the `schema_locked` table storage parameter could be bypassed by combining `SET (schema_locked=false)` with other schema changes in the same `ALTER TABLE` statement using comma syntax. Schema-locked tables now correctly reject such combined statements. ### Performance improvements * Triggers now perform the descriptor lookup for `TG_TABLE_SCHEMA` against a cache. This can significantly reduce trigger planning latency in multi-region databases. * `AFTER` triggers now use a cache for descriptor lookups of `TG_TABLE_SCHEMA`, which can significantly reduce trigger planning latency. ## v26.1.0-alpha.2 Release Date: December 11, 2025 ### Downloads CockroachDB v26.1.0-alpha.2 is a testing release. Testing releases are intended for testing and experimentation only, and are not qualified for production environments and not eligible for support or uptime SLA commitments. Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.
Operating SystemArchitectureFull executableSQL-only executable
LinuxIntelcockroach-v26.1.0-alpha.2.linux-amd64.tgz
(SHA256)		cockroach-sql-v26.1.0-alpha.2.linux-amd64.tgz
(SHA256)
ARMcockroach-v26.1.0-alpha.2.linux-arm64.tgz
(SHA256)		cockroach-sql-v26.1.0-alpha.2.linux-arm64.tgz
(SHA256)
Mac
(Experimental)		Intelcockroach-v26.1.0-alpha.2.darwin-10.9-amd64.tgz
(SHA256)		cockroach-sql-v26.1.0-alpha.2.darwin-10.9-amd64.tgz
(SHA256)
ARMcockroach-v26.1.0-alpha.2.darwin-11.0-arm64.tgz
(SHA256)		cockroach-sql-v26.1.0-alpha.2.darwin-11.0-arm64.tgz
(SHA256)
Windows
(Experimental)		Intelcockroach-v26.1.0-alpha.2.windows-6.2-amd64.zip
(SHA256)		cockroach-sql-v26.1.0-alpha.2.windows-6.2-amd64.zip
(SHA256)
### Docker image [Multi-platform images](https://docs.docker.com/build/building/multi-platform) include support for both Intel and ARM. Multi-platform images do not take up additional space on your Docker host. Within the multi-platform image, both Intel and ARM images are **generally available** for production use. To download the Docker image: ```shell theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}} docker pull cockroachdb/cockroach:v26.1.0-alpha.2 ``` ### Security updates * A new, optional flag for `cockroach start` restricts the `root` user from logging in to the system via both SQL and RPC connections. This change affects the unstated, unchangeable root access rule and addresses compliance requirements. It is currently available in Limited Access. * A new `debug_user` certificate has also been introduced for privileged RPC access to collect debug zip information, which would otherwise be unavailable when `root` is restricted. `debug_user` must be created manually with the `CREATE USER` command and can be audited using `SHOW USERS`. It has privileged access to the `serverpb` admin and status endpoints required for debug zip collection. * Ensure that none of the certificates used by the cluster or SQL/RPC clients have "root" in the SAN (Subject Alternative Name) fields, as the flag will block access to those clients. ### SQL language changes * Added a new session variable, `use_swap_mutations`, which controls whether the new update swap and delete swap operators are enabled for use by `UPDATE` and `DELETE` statements. * Fixed a bug where the results of `ALTER SEQUENCE` 's increment and `SELECT nextval()` operations were not as expected. The value of a sequence after an `ALTER SEQUENCE` statement has executed on it is now consistent with a sequence created with those values. * SQL statements executed in stored procedures and user-defined functions now record SQL statistics, including latencies and execution metrics. These statistics appear on the **SQL Activity** and **Insights** pages of the DB Console. Limitation: SQL statements within a stored procedure or user-defined function are not collected for active statement diagnostics requests. Statement diagnostics remain available for top-level statement executions. * The `ALTER COLUMN...` sequence identity commands are run by the declarative schema changer. * The `cumulative time spent waiting in admission control` is now displayed in `EXPLAIN ANALYZE` output when it is non-zero. This helps identify delays caused by admission control during query execution. * Restarting a sequence with an updated increment has the expected initial value. * The `cumulative time spent waiting in admission control` reported in `EXPLAIN ANALYZE` now includes the time spent in quorum replication flow control. This update enhances the precision of wait time analysis, offering a more accurate depiction of query execution time by considering additional wait durations within the quorum replication processes. * Added a new "hint injection" ability that allows operators to dynamically inject inline hints into statements, without modifying the text of those statements. Hints can be injected using the built-in function `crdb_internal.inject_hint` with the target statement fingerprint to rewrite. For example, to add an index hint to the statement `SELECT * FROM my_table WHERE col = 3`, use: ```text theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}} SELECT crdb_internal.inject_hint( 'SELECT * FROM my_table WHERE col = _', 'SELECT * FROM my_table@my_table_col_idx WHERE col = _' ); ``` Whenever a statement is executed matching statement fingerprint `SELECT * FROM my_table WHERE col = _`, it will first be rewritten to include the injected index hint. - `ALTER TABLE... SET SCHEMA` is supported by the declarative schema changer. - `kv cpu time` is now displayed in `EXPLAIN ANALYZE`, providing insights into the CPU resources used by KV operations during query execution. - CockroachDB now negotiates the pgwire protocol version with PostgreSQL 18+ clients that request protocol version 3.2. Previously, connections from these clients would fail with an "unknown protocol version" error. The server now sends a `NegotiateProtocolVersion` message to indicate it supports version 3.0, allowing the connection to proceed normally. ### Operational changes * The `allow_unsafe_internals` setting now defaults to `false`, restricting access to the `system` and `crdb_internal` namespaces. Queries to these namespaces will now fail unless access is manually enabled. Usage is also audited. * Jobs that are paused due to a specific reason, including jobs which pause themselves when encountering errors such as running out of disk space, now record that reason in their displayed status field of `SHOW JOBS`. * The following metrics are now marked as essential to support end-user troubleshooting of authentication latency issues: * `auth.jwt.conn.latency` * `auth.cert.conn.latency` * `auth.password.conn.latency` * `auth.ldap.conn.latency` * `auth.gss.conn.latency` * `auth.scram.conn.latency` * `auth.ldap.conn.latency.internal` ### DB Console changes * The log of messages and events recorded by a job is now shown to non-admin users on the DB Console Jobs page. * The DB Console now accurately displays **vCPU** counts on the **Overview** page instead of operating system CPU counts. This update uses cgroups to provide a correct vCPU measurement, reflecting reserved compute resources in Kubernetes and other virtualized environments. * Jobs which are paused for a specific reason now show that reason, and are highlighted in the UI. * The `kvCPUTimeNanos` is now recorded in `crdb_internal.statement_statistics` and `crdb_internal.transaction_statistics`. In the DB Console, a **KV CPU Time** column is now displayed in the **SQL Activity** > **Statements** and **Transactions** pages, allowing you to monitor and analyze the CPU time consumed by KV operations during query execution. * The `admissionWaitTime` is now recorded in `crdb_internal.statement_statistics` and `crdb_internal.transaction_statistics`. In the DB Console, an **Admission Wait Time** column is now displayed in the **SQL Activity** > **Statements** and **Transactions** pages. ### Bug fixes * Fixed a bug that could cause an internal error in some cases for PL/pgSQL routines that perform database reads within an exception block. * Fixed a bug where a SQL statement with side effects (e.g., `INSERT` ) inside a PL/pgSQL routine could be dropped if it used an `INTO` clause and none of the target variables were referenced. This bug had been present since v23.2. * Fixed a bug where renaming a column that participated in multiple hash-sharded indexes would fail. * Fixed a bug where `ORDER BY` clauses in user-defined set-returning SQL functions with `OUT` parameters were ignored when the function was called directly in a `SELECT` list (e.g., `SELECT f()` ). The ordering is now properly preserved and enforced. * The pgwire server now exits promptly on context cancellation. * Fixed a bounded memory leak that could occur during table statistics collection on tables that contain both very wide (10 KiB or more) and small (under 400B) `BYTES` -like values within the same row, along with virtual computed columns. This bug had been present since stats collection on virtual computed columns was introduced in v24.1. * Temporary schema cleanup no longer retries after poisoned transaction errors, reducing log noise. * When changing the time interval on the **Metrics** page, the DB Console previously sent duplicate requests for metrics data. This has been fixed, and the UI now issues a single, efficient request when updating the time interval. ### Performance improvements * Added new `update swap` and `delete swap` operators that allow some `UPDATE` and `DELETE` statements to execute in 1 roundtrip instead of 2 roundtrips. These operators can be used when: * All columns in the primary index are constrained to a single exact value by the `WHERE` clause; * Only a single row is modified; * There are no foreign-key checks or cascades; * There are no uniqueness checks; * There are no check constraints; * There are no vector indexes modified; * There are no passthrough columns to `RETURNING`; * There are no triggers; * The table only uses a single column family; * There are no mutation columns or mutation indexes (i.e., the table is not undergoing an `ALTER` ); * There are no columns using composite encoding (e.g., `DECIMAL`, `FLOAT`, `JSON`, etc.). * The optimizer now collapses repeated `%` wildcard characters in `LIKE` patterns. This may improve performance of queries using such patterns. * More of the CPU usage of LDR jobs is subject to background job admission control limits. ## v26.1.0-alpha.1 Release Date: December 4, 2025 ### Downloads CockroachDB v26.1.0-alpha.1 is a testing release. Testing releases are intended for testing and experimentation only, and are not qualified for production environments and not eligible for support or uptime SLA commitments. Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.
Operating SystemArchitectureFull executableSQL-only executable
LinuxIntelcockroach-v26.1.0-alpha.1.linux-amd64.tgz
(SHA256)		cockroach-sql-v26.1.0-alpha.1.linux-amd64.tgz
(SHA256)
ARMcockroach-v26.1.0-alpha.1.linux-arm64.tgz
(SHA256)		cockroach-sql-v26.1.0-alpha.1.linux-arm64.tgz
(SHA256)
Mac
(Experimental)		Intelcockroach-v26.1.0-alpha.1.darwin-10.9-amd64.tgz
(SHA256)		cockroach-sql-v26.1.0-alpha.1.darwin-10.9-amd64.tgz
(SHA256)
ARMcockroach-v26.1.0-alpha.1.darwin-11.0-arm64.tgz
(SHA256)		cockroach-sql-v26.1.0-alpha.1.darwin-11.0-arm64.tgz
(SHA256)
Windows
(Experimental)		Intelcockroach-v26.1.0-alpha.1.windows-6.2-amd64.zip
(SHA256)		cockroach-sql-v26.1.0-alpha.1.windows-6.2-amd64.zip
(SHA256)
### Docker image [Multi-platform images](https://docs.docker.com/build/building/multi-platform) include support for both Intel and ARM. Multi-platform images do not take up additional space on your Docker host. Within the multi-platform image, both Intel and ARM images are **generally available** for production use. To download the Docker image: ```shell theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}} docker pull cockroachdb/cockroach:v26.1.0-alpha.1 ``` ### General changes * Docker images now use UBI 10 as the base image. * The changefeed bulk delivery setting was made optional. * To improve changefeed performance, the session variable `create_table_with_schema_locked` is enabled by default. This means all new tables are created with the `schema_locked` storage parameter. `schema_locked` must be explicitly unset for explicit transactions or for schema changes that do not support automatic disabling (e.g., `ALTER TABLE... SET LOCALITY` ). ### SQL language changes * Index acceleration is now supported for a subset of `jsonb_path_exists` filters used in the `WHERE` clause. Given `jsonb_path_exists(json_obj, json_path_expression)`, inverted indexes are supported only when the `json_path_expression` matches one of the following patterns: * The `json_path_expression` must not be in STRICT mode. * Keychain mode: `$. [key|wildcard].[key|wildcard]...`. In this mode, a prefix span is generated for the inverted expression. * Filter with end value mode, using an equality check: `$. [key|wildcard]? (@.[key|wildcard].[key|wildcard]... == [string|number|null|boolean])`. In this mode, since the end value is fixed, a single-value span is generated. The following cases are not supported: * `$` * `$[*]` * `$.a.b.c == 12`, `$.a.b.c > 12`, or `$.a.b.c < 12` (operation expressions) * `$.a.b? (@.a > 10)` (filter with an inequality check) * `SHOW CHANGEFEED JOBS` now includes a `database_name` field that displays the database name for database-level changefeeds. For table-level changefeeds, this field is `null`. For database-level changefeeds, the `full_table_names` field now returns an empty list by default and displays only the total count of watched tables. To view the full list of watched tables (as in previous versions), use the new `WITH WATCHED_TABLES` option: ```sql theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}} SHOW CHANGEFEED JOBS WITH WATCHED_TABLES; ``` This change improves performance when displaying database-level changefeeds that may track many tables. * Added a clamp for the estimated selectivity of inequality predicates that are unbounded on one or both sides (e.g., `x > 5`). This reduces the risk of a catastrophic underestimate that causes the optimizer to choose a poorly-constrained scan. The feature is disabled by default and can be enabled with the session setting `optimizer_clamp_inequality_selectivity`. * Added a clamp on row-count estimates for very large tables to ensure the optimizer assumes at least one distinct value will be scanned. This reduces the risk of a catastrophic underestimate. The feature is off by default and controlled by the `optimizer_clamp_low_histogram_selectivity` session setting. * The optimizer can now use table statistics that merge the latest full statistic with all newer partial statistics, including those over arbitrary constraints over a single span. * Added the `sql.catalog.allow_leased_descriptors.enabled` cluster setting, which is false by default. When set to true, queries that access the `pg_catalog` or `information_schema` can use cached leased descriptors to populate the data in those tables, with the tradeoff that some of the data could be stale. * Added a default-off cluster setting (`sql.log.scan_row_count_misestimate.enabled`) that enables logging a warning on the gateway node when optimizer estimates for scans are inaccurate. The log message includes the table and index being scanned, the estimated and actual row counts, the time since the last table stats collection, and the table's estimated staleness. * Fixed a bug where the results of `ALTER SEQUENCE`'s increment and `SELECT nextval()` operations were not as expected. The value of a sequence after an `ALTER SEQUENCE` statement has executed on it is now consistent with a sequence created with those values. * Added changefeed setting `range_distribution_strategy` with values `'default'` or `'balanced_simple'`. This new per-changefeed setting overrides the cluster setting `changefeed.default_range_distribution_strategy` where both exist. Example: ```sql theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}} CREATE CHANGEFEED FOR x into 'null://' WITH range_distribution_strategy='balanced_simple'; ``` * Added the `INSPECT` command, which runs consistency validation check jobs against tables or databases and specified indexes. * Added support for collecting partial statistics when the given `WHERE` clause implies the predicate of a partial index with the requested column as the first key column. For example: ```text theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}} CREATE TABLE t (a INT, INDEX idx_partial (a) WHERE a > 5); CREATE STATISTICS pstat ON a FROM t WHERE a > 7; ``` * The `row_security` session variable now behaves as it does in PostgreSQL, allowing users to detect when RLS is applied. * Added the `bulkio.index_backfill.vector_merge_batch_size` cluster setting to control how many vectors to merge into a vector index per transaction during create operations. The setting defaults to `3`. * Updated the scan misestimate logging, which is controlled by the `sql.log.scan_row_count_misestimate.enabled` cluster setting, to use structured logging. The logs now include the scanned table and index, the estimated and actual row counts, the time since the last table statistics collection, and the table's estimated staleness. * The `EXPERIMENTAL SCRUB` command is deprecated. Use the `INSPECT` command for data consistency validation. * `INSPECT` supports a `DETACHED` option to run the operation without waiting for it. * `ALTER TABLE... DROP STORED` statements are now executed internally by the declarative schema changer. * Added a `sql.statements.rows_read.count` metric that counts the number of index rows read by SQL statements. * Added the `EXPLAIN (FINGERPRINT)` statement, which returns normalized statement fingerprints with constants replaced by underscores. For example, `EXPLAIN (FINGERPRINT) SELECT * FROM t WHERE a = 123` returns `SELECT * FROM t WHERE a = _`. * Introduced two new settings to control the use of canary statistics in query planning: * Cluster setting `sql.stats.canary_fraction` (float, range \[0, 1], default: 0): Controls what fraction of queries use "canary statistics" (newly collected stats within their canary window) versus "stable statistics" (previously proven stats). For example, a value of `0.2` means 20% of queries will use canary stats while 80% use stable stats. The selection is atomic per query: if a query is chosen for canary evaluation, it uses canary statistics for **all** tables it references (where available). A query never uses a mix of canary and stable statistics. * Session variable `canary_stats_mode` (enum: \{auto, off, on}, default: auto): * `on`: All queries in the session use canary stats for planning. * `off`: All queries in the session use stable stats for planning. * `auto`: The system decides based on `sql.stats.canary_fraction` for each query execution. * Introduced a new table storage parameter, `sql_stats_canary_window`, to enable gradual rollout of newly collected table statistics. It takes a duration string as the value. When set with a positive duration, the new statistics remain in a "canary" state for the specified duration before being promoted to stable. This allows for controlled exposure and intervention opportunities before statistics are fully deployed across all queries. * Introduced `SHOW FINGERPRINTS FOR TABLE`, which produces an FNV hash for each index in a table. FNV is used for performance reasons and is sensitive to changes in the underlying data, including `NULL`s. * The `optimizer_clamp_low_histogram_selectivity` and `optimizer_clamp_inequality_selectivity` settings are now on by default. This causes the optimizer to assume that at least one distinct value "passes" each filter in a query, and that open-ended inequality filters select at least 1/10000 rows from the table. This reduces the chances of a catastrophic row count underestimate when stats are inaccurate. * The `ALTER TABLE... SET/ADD GENERATED AS IDENTITY` statement is supported by the declarative schema changer in v26.1 and later. * `EXPLAIN` and `EXPLAIN ANALYZE` will now display the number of hints from `system.statement_hints` applied to the executed statement. * The **Plan Details** in the **Statement Activity** page of the DB Console now show whether any hints from `system.statement_hints` were applied to the statement execution. ### Operational changes * The metrics `sql.select.started.count`, `sql.insert.started.count`, `sql.update.started.count`, and `sql.delete.started.count` are now emitted with labels under the common metric name `sql.started.count`, using a `query_type` label to distinguish each operation. * Added the cluster setting `storage.unhealthy_write_duration` (defaults to 20s), which is used to indicate to the allocator that a store's disk is unhealthy. The cluster setting `kv.allocator.disk_unhealthy_io_overload_score` controls the overload score assigned to a store with an unhealthy disk, where a higher score results in preventing lease or replica transfers to the store, or shedding of leases by the store. The default value of that setting is 0, so the allocator behavior is unaffected. * Added two new changefeed metrics for tracking the max skew between a changefeed's slowest and fastest span/table. The metrics are gauge metrics with the names `changefeed.progress_skew.{span}` and `changefeed.progress_skew.{table}`. * Added the cluster setting `storage.snapshot.recreate_iter_duration` (default 20s), which controls how frequently a long-lived storage engine iterator, backed by an engine snapshot, will be closed and recreated. Currently, it is only used for iterators used in rangefeed catchup scans. * Added cluster setting `sql.schema.approx_max_object_count` (default: 20,000) to prevent creation of new schema objects when the limit is exceeded. The check uses cached table statistics for performance and is approximate - it may not be immediately accurate until table statistics are updated by the background statistics refreshing job. Clusters that have been running stably with a larger object count should raise the limit or disable the limit by setting the value to 0. In future releases, the default value for this setting will be raised as more CockroachDB features support larger object counts. * Cleaned up redundant and misleading metrics. * Fixed the `changefeed.parallel_io_pending_rows` metric's y-axis label to match the metric's definition. * Added a metric called `changefeed.parallel_io_workers` to track the number of workers in ParallelIO. * Events related to changefeed operations are now routed to the `CHANGEFEED` channel, while sampled queries and transactions, along with certain SQL performance events, are logged to `SQL_EXEC`. To continue using the previous logging channels, set `log.channel_compatibility_mode.enabled` to `true`. * Successfully completed automatic SQL stats collecton jobs are now automatically purged rather than being retained for the full default job retention period. * The cluster setting `storage.snapshot.recreate_iter_duration` (default `20s` ) controls how frequently a long-lived engine iterator, backed by an engine snapshot, will be closed and recreated. Currently, it is only used for iterators used in rangefeed catchup scans. * Add support for `CREATE LOGICAL REPLICATION STREAM` in situations where the source table has a column with a sequence expression. ### Command-line changes * `cockroach workload run` commands now offer a `--with-changefeed` flag to additionally run a changefeed that watches for writes to the workload's tables. ### DB Console changes * The **SQL** dashboard has been enhanced with additional insights. * The **Transaction Restarts** dashboard now displays `txn.restarts.txnpush` and `txn.restarts.unknown` metrics. - A new **Failed SQL Connections** graph shows failed SQL connection attempts. A new **SQL Queries Within Routines Per Second** dashboard reports on `SELECT`, `UPDATE`, `INSERT`, and `DELETE` operations executed within routines. * A new **Table Statistics Collections** dashboard provides information on auto, auto partial, and manual statistics collections. \#155203 * The background (elastic) store graphs for exhausted duration, and the wait duration histogram, have been separated from the foreground (regular) graphs. ### Bug fixes * Previously, CockroachDB would omit execution statistics in `EXPLAIN ANALYZE` output for mutation nodes when a `RETURNING` clause was used. The bug was present since before v21.1 and is now fixed. * Fixed a bug where CockroachDB could encounter a `vector encoder doesn't support ForcePut yet` error when executing `COPY` commands concurrently with certain schema changes. The bug had existed since before v23.2. * Fixed a bug causing a `READ COMMITTED` or `SNAPSHOT` isolation transaction to be committed despite returning a non-ambiguous error. * Fixed a bug in type-checking placeholders with `UNKNOWN` types. It could cause incorrect results in some cases. * Fixed a bug where `EXPORT CSV` and `EXPORT PARQUET` could cause a node crash when their result rows were used as input to a mutation, such as an `INSERT`, within the same SQL statement. This bug had been present since before v22.1. * **Idle latency** on the **Transaction Details** page in the DB Console is now reported more accurately. Previously, transactions that used prepared statements (e.g., with placeholders) overcounted idle time, while those that included observer statements (common in the SQL CLI) undercounted it. * Fixed a bug that caused panics when executing `COPY` into a table with hidden columns and expression indexes. The panic only occurred when the session setting `expect_and_ignore_not_visible_columns_in_copy` was enabled. This bug was introduced with `expect_and_ignore_not_visible_columns_in_copy` in v22.1.0. * Vector index backfill jobs now correctly report progress in the `SHOW JOBS` output. * Fixed a bug where `RESTORE` of a database with a `SECONDARY REGION` did not apply the lease preferences for that region. * Fixed a bug where a changefeed could perform many unnecessary job progress saves during an initial scan. * Fixed a bug where CockroachDB would not log events for `TxnRowsRead` and `TxnRowsWritten` guardrails for internal queries into the `SQL_INTERNAL_PERF` logging channel. The bug was present since v21.2. * Fixed a bug that caused internal errors for `INSERT.. ON CONFLICT.. DO UPDATE` statements when the target table had both a computed column and a `BEFORE` trigger. This bug was present since triggers were introduced in v24.3.0. * Fixed a bug where a changefeed targeting only a subset of a table's column families could become stuck. * Fixed a bug where CockroachDB would hit an internal error when performing an inverted join using an inverted index in which the first prefix column had `DESC` direction. The bug was present since v21.1. * Fixed a bug where the `kvflowcontrol.send_queue.scheduled.force_flush` metric was missing a decrement, resulting in a value of greater than `0` even when there was no ongoing force flush. * Fixed a bug that would cause `WITH READ VIRTUAL CLUSTER` to be ignored if any other options were passed when running `CREATE VIRTUAL CLUSTER FROM REPLICATION`. * Internal assertions that verify `NumRange = 0` in the first histogram bucket, used to catch malformed statistics, now run only in test builds to avoid crashing production queries. * Fixed a bug in which range counts in table statistics histograms were not handled correctly after a user-defined `ENUM` type was modified. * Fixed a bug in the `cockroach node drain` command where draining a node using virtual clusters (such as clusters running Physical Cluster Replication (PCR)) could return before the drain was complete, possibly resulting in shutting down the node while it still had active SQL clients and range leases. * Fixed a bug where a race condition in range splits could result in a regressed Raft state on a post-split range. This condition was extremely rare, and only observed during internal testing. * Corrected a potential deadlock during vector index creation. * Fixed a bug that would result in a node crash if a PCR or LDR URI used `sslinline=true` with `sslmode=disable`. * Fixed a bug where CockroachDB could corrupt the first bucket of table statistic histograms in certain cases, causing underestimates for range counts near the lower end of the domain. * Added proper dependency handling when adding a constraint with `NOT VALID` that references a user-defined function (UDF). * Fixed a bug that prevented the optimizer from recognizing correlated filters when one of the filtered columns had a single distinct value across all rows. This could lead to suboptimal query plans in some cases. * The username remapping functionality specified by the `server.identity_map.configuration` cluster setting now matches identities and usernames with a case-insensitive comparison. * Previously, the forecasted statistics shown in `SHOW STATISTICS... WITH FORECAST` could be inconsistent with those in the stats cache, depending on whether `WITH MERGE` was specified. Forecasted statistics are now displayed consistently, regardless of the `WITH MERGE` clause. * Fixed a bug where CockroachDB could crash when executing `EXPLAIN ANALYZE` statements using the pausable portal model. This would occur when the query was executed via the extended PGWire protocol ( `Parse`, `Bind`, `Execute` ) with the `multiple_active_portals_enabled` session variable set. The bug was present since v23.2. * `INSPECT` can now be run on tables with indexes that store `REFCURSOR` -typed columns. * Fixes a bug where `DROP SCHEMA CASCADE` could run into an error with complex references from triggers. * Fixed a bug where the job responsible for compacting stats for the SQL activity state could enter an unschedulable state. Fixes: #155165 * Fixed a bug where reads and writes performed by routines (user-defined functions and stored procedures) and apply joins were not included in `bytes read`, `rows read`, and `rows written` statement execution statistics. This bug had been present since before v23.2. * `INSPECT` now correctly checks index consistency at the historical timestamp when using `AS OF SYSTEM TIME`, even for spans with no current data. * The `INSPECT` statement now detects dangling secondary index entries even when the primary index spans contain no data. * Fixed an internal error that could occur when replacing a user-defined function or stored procedure using `CREATE OR REPLACE`, if the existing signature included multiple `DEFAULT` expressions. This bug was introduced in v24.2, when support for `DEFAULT` expressions was added. * `INSPECT` no longer fails when checking index consistency on indexes with virtual key columns. Such indexes will now be skipped. * Fixed a bug where DML statements on regional by row tables with unique indexes that do not reference the region could sometimes fail under `READ COMMITTED` isolation. * Fixed a bug where Zone Config Extensions incorrectly prevented users from removing non-voting read replicas from multi-region databases. Users can now set `num_replicas` equal to `num_voters` to remove read replicas while maintaining the required number of voting replicas for their database's survival goal. This allows reducing storage costs without compromising availability guarantees. * Fixed a bug in the `ltree2text` built-in function where the returned `TEXT` value was incorrectly wrapped in single quotes. This bug had been present since the `ltree2text` function was introduced in v26.1.0-alpha.1. * Fixed a bug that caused incorrect results for queries that filter indexed `LTREE` columns with the `<@` (contained-by) operator. This bug was present since v26.1.0-alpha.1. * Fixed a bug where the "atomic" `COPY` command (controlled via the `copy_from_atomic_enabled` session setting, `true` by default) could encounter `RETRY_COMMIT_DEADLINE_EXCEEDED` transaction errors if the whole command took 1 minute or more. This bug occurred only when the vectorized engine was used for `COPY`. * Fixed a bug that caused transactions to fail with the error message: `failed indeterminate commit recovery: programming error: timestamp change by implicitly committed transaction`. * Fixed a bug in JSONPath index acceleration where queries using `jsonb_path_exists` with a root key (e.g., `$.b` ) incorrectly returned no results when the queried JSON was an array. This fix enables unwrapping a single array layer at the root, allowing the path to be evaluated against each element. Only v25.4 releases were affected. * Fixed a bug that prevents large `TRUNCATE` operations from completing due to `command is too large` errors. * Fixed a bug that caused incorrect `gossip.callbacks.pending_duration` metric values to be recorded. * Fixed a bug where transactions running concurrently with a `GRANT` or `REVOKE` on virtual tables or via external connections could observe modifications incorrectly. * Fixed a bug where CockroachDB could encounter an internal error when evaluating a `COPY FROM` command in a transaction after it was rolled back to a savepoint. The bug was present since before v23.2. * Fixed a bug that could cause internal errors for queries using generic query plans with `NULL` placeholder values. * Fixed a bug that could cause a schema change to be stuck in the reverting state if the `infer_rbr_region_col_using_constraint` storage parameter was being set at the same time as adding a constraint that had a foreign key violation. ### Performance improvements * The cost of generic query plans is now calculated based on worst-case selectivities for placeholder equalities (e.g., `x = $1` ). This reduces the chance of suboptimal generic query plans being chosen when `plan_cache_mode=auto`. * TTL jobs now checkpoint their progress, allowing them to resume without reprocessing already completed spans after a restart. * Queries with filters in the form `a LIKE b ESCAPE '\'` are now index-accelerated in certain cases where they were not before. * The optimizer will no longer choose a generic query plan with unbounded cardinality over a custom query plan with bounded cardinality, regardless of `optimizer_prefer_bounded_cardinality`, better optimizing such queries. * Optimized validation queries during `ALTER PRIMARY KEY` to avoid counting the primary key multiple times. * The optimizer now splits disjunctions on the same column into unions when there are multiple partial indexes with different predicates referencing that column. ### Build changes * Upgraded to Go version 1.25.3 ### Miscellaneous * Added initial and catchup scan metrics to Physical Cluster Replication (PCR) under `physical_replication.scanning_ranges` and `physical_replication.catchup_ranges`. * Added a retry policy for Azure Blob Storage with a default of 60 seconds to mitigate occasional stuck operations. The retry policy is configurable with the `cloudstorage.azure.try.timeout` setting. * Logical Data Replication (LDR) now updates the `logical_replication.scanning_ranges` and `logical_replication.catchup_ranges` metrics during fast initial scan. * Added the `jobs.registry.max_adoptions_per_loop` cluster setting to configure the maximum number of jobs a node can adopt per adoption loop. * Fixed a bug that prevented admin users from having full access to external connections created by other users. * LDR no longer requires the database name to be specified in the external connection URI when setting up a bidirectional stream. * Span config reconciliation jobs no longer fail on the destination after failover from a PCR stream of a system virtual cluster. * Added support of partial indexes to Logical Data Replication, tolerant of mismatched column IDs in the source and destination tables. * Display whether build is FIPS-enabled in `cockroach version`