<?xml version="1.0" encoding="utf-8"?>
    <feed xmlns="http://www.w3.org/2005/Atom">
      <title>Changelog — PlanetScale</title>
      <subtitle>The latest PlanetScale features and product launches.</subtitle>
      <link href="https://planetscale.com" />
      <link rel="alternate" type="text/html" hreflang="en" href="https://planetscale.com/changelog" />
      <link rel="self" type="application/atom+xml" href="https://planetscale.com/changelog/feed.atom" />
      <id>https://planetscale.com/changelog/feed.atom</id>
      <updated>2026-11-17T22:43:00.000Z</updated>

  
      <entry>
        <title>Start Insights Agent runs from the CLI and MCP</title>
        <link href="https://planetscale.com/changelog/insights-agent-cli-and-mcp" />
        <id>https://planetscale.com/changelog/insights-agent-cli-and-mcp</id>
        <published>2026-11-17T22:43:00.000Z</published>
        <updated>2026-11-17T22:43:00.000Z</updated>
        <content type="html"><![CDATA[<p>You can now start, review, cancel, and schedule Insights Agent runs from the CLI and the <a href="https://planetscale.com/docs/mcp-server">MCP server</a>. Pass up to five slow query fingerprints or schema recommendations to start a run, or turn a <code>slow_query</code> or <code>schema_recommendation</code> schedule on and off.</p><p>Use <code>pscale insights agent</code>, or <code>planetscale_start_insights_agent_run</code> and <code>planetscale_update_insights_agent_schedule</code> from MCP. Service tokens need <code>read_insights_agent</code> to list and show runs, and <code>write_insights_agent</code> to start, cancel, or change schedules.</p><pre data-language="bash">pscale insights agent runs create &lt;database&gt; &lt;branch&gt; --org &lt;org&gt; --fingerprint &lt;fingerprint&gt; --keyspace &lt;keyspace&gt;
pscale insights agent schedules update &lt;database&gt; &lt;branch&gt; slow_query --org &lt;org&gt; --enabled --frequency week --day-of-week 1 --time 03:00 --time-zone America/New_York
</pre><p><strong><a href="https://planetscale.com/docs/cli/insights">CLI insights docs</a></strong> · <strong><a href="https://planetscale.com/docs/mcp-server">MCP docs</a></strong> · <strong><a href="https://planetscale.com/docs/insights-agent">Insights Agent</a></strong> · <strong><a href="https://planetscale.com/docs/api/service-tokens">Service tokens</a></strong></p>]]></content>
        <summary><![CDATA[You can now start, review, cancel, and schedule Insights Agent runs from the CLI and the MCP server. Pass up to five slow query fingerprints or schema recommendations to start a run, or turn a slow_query or schema_recommendation schedule on and off.]]></summary>
      </entry>
    
      <entry>
        <title>Require multi-factor authentication for your organization</title>
        <link href="https://planetscale.com/changelog/require-multi-factor-authentication" />
        <id>https://planetscale.com/changelog/require-multi-factor-authentication</id>
        <published>2026-11-17T20:13:00.000Z</published>
        <updated>2026-11-17T20:13:00.000Z</updated>
        <content type="html"><![CDATA[<p>Organization Administrators can now require multi-factor authentication for every member from the organization&#x27;s <a href="https://app.planetscale.com/~/settings/authentication">authentication settings</a>.</p><p>Members without multi-factor authentication get notified at least seven days before the requirement takes effect. Once it does, they can&#x27;t access the organization until they add an authenticator app, a passkey, or a security key.</p><p><strong><a href="https://planetscale.com/docs/security/multi-factor-authentication#require-mfa-for-an-organization">Read more</a></strong></p>]]></content>
        <summary><![CDATA[Organization Administrators can now require multi-factor authentication for every member from the organization's authentication settings.]]></summary>
      </entry>
    
      <entry>
        <title>Authenticate to the PlanetScale API from Cursor Cloud Agents with OpenID Connect</title>
        <link href="https://planetscale.com/changelog/oidc-authentication-cursor" />
        <id>https://planetscale.com/changelog/oidc-authentication-cursor</id>
        <published>2026-11-17T18:22:29.000Z</published>
        <updated>2026-11-17T18:22:29.000Z</updated>
        <content type="html"><![CDATA[<p>You can now authenticate to the PlanetScale API from Cursor Cloud Agents using OpenID Connect (OIDC). An agent exchanges its Cursor OIDC token for a short-lived service token, so you no longer need to store long-lived PlanetScale credentials in your Cursor secrets.</p><p>Create a Cursor trust policy in the <a href="https://app.planetscale.com/~/settings/oidc">dashboard</a> for your Cursor team, then give the agent instructions to request a token and exchange it with the PlanetScale API.</p><p><strong><a href="https://planetscale.com/docs/api/oidc#cursor">Read more</a></strong></p>]]></content>
        <summary><![CDATA[You can now authenticate to the PlanetScale API from Cursor Cloud Agents using OpenID Connect (OIDC).An agent exchanges its Cursor OIDC token for a short-lived service token, so you no longer need to store long-lived PlanetScale credentials in your Cursor secrets.]]></summary>
      </entry>
    
      <entry>
        <title>Set storage IOPS and throughput when restoring Postgres backups</title>
        <link href="https://planetscale.com/changelog/postgres-restore-storage-iops-throughput" />
        <id>https://planetscale.com/changelog/postgres-restore-storage-iops-throughput</id>
        <published>2026-11-17T15:55:00.000Z</published>
        <updated>2026-11-17T15:55:00.000Z</updated>
        <content type="html"><![CDATA[<p>Postgres backup restores will now let you set storage IOPS and throughput for the new branch. Large restores are often limited by disk throughput, so this lets you speed up a restore without choosing a bigger cluster size than the branch needs.</p><p>You&#x27;ll find the new settings in the <strong>Restore to new branch</strong> dialog for branches on AWS network-attached storage. The settings stay on the restored branch, and you can change them later from its storage settings.</p><p>You can also set them from the CLI with <code>--storage-iops</code> and <code>--storage-throughput</code>:</p><pre data-language="bash">pscale backup restore &lt;DATABASE_NAME&gt; &lt;NEW_BRANCH_NAME&gt; &lt;BACKUP_ID&gt; \
  --storage-iops 5000 --storage-throughput 300
</pre><p>Through the API, set <code>storage_iops</code> and <code>storage_throughput_mibs</code> in the <code>storage</code> object when you <a href="https://planetscale.com/docs/api/reference/create_branch">create a branch</a> from a backup or a point in time.</p><p><strong><a href="https://planetscale.com/docs/postgres/backups#creating-a-restored-branch">Read more about restoring Postgres backups</a></strong></p>]]></content>
        <summary><![CDATA[Postgres backup restores will now let you set storage IOPS and throughput for the new branch. Large restores are often limited by disk throughput, so this lets you speed up a restore without choosing a bigger cluster size than the branch needs.]]></summary>
      </entry>
    
      <entry>
        <title>Duplicate and edit service tokens</title>
        <link href="https://planetscale.com/changelog/duplicate-and-edit-service-tokens" />
        <id>https://planetscale.com/changelog/duplicate-and-edit-service-tokens</id>
        <published>2026-11-17T00:40:00.000Z</published>
        <updated>2026-11-17T00:40:00.000Z</updated>
        <content type="html"><![CDATA[<p>You can now duplicate a service token from its actions menu in the dashboard. The copy gets a new ID and secret with the same permissions as the original.</p><p>The same menu also has a new <strong>Edit</strong> action to rename a service token or change when it expires.</p><p>Both are available in the API with the <a href="https://planetscale.com/docs/api/reference/duplicate_service_token">duplicate a service token</a> and <a href="https://planetscale.com/docs/api/reference/update_service_token">update a service token</a> endpoints, and in the CLI with <a href="https://planetscale.com/docs/cli/service-token"><code>pscale service-token duplicate</code></a> and <a href="https://planetscale.com/docs/cli/service-token"><code>pscale service-token update</code></a> (pscale v0.353.0).</p>]]></content>
        <summary><![CDATA[You can now duplicate a service token from its actions menu in the dashboard. The copy gets a new ID and secret with the same permissions as the original.]]></summary>
      </entry>
    
      <entry>
        <title>Revoke all sessions and member tokens</title>
        <link href="https://planetscale.com/changelog/revoke-sessions-and-member-tokens" />
        <id>https://planetscale.com/changelog/revoke-sessions-and-member-tokens</id>
        <published>2026-11-16T23:15:00.000Z</published>
        <updated>2026-11-16T23:15:00.000Z</updated>
        <content type="html"><![CDATA[<p>If you lose a device, you can now revoke all of your sessions from your <a href="https://app.planetscale.com/settings/account">account settings</a>. This signs you out of PlanetScale in every other browser and revokes your pscale CLI logins and the OAuth applications you authorized, such as MCP clients. The organization service tokens are not affected.</p><p>Organization Administrators can also revoke a member&#x27;s tokens from the <strong>Members</strong> settings page. The member&#x27;s pscale CLI logins and the OAuth applications they authorized lose access to that organization.</p><p><strong><a href="https://planetscale.com/docs/security/authentication-methods#revoke-all-sessions">Read more about revoking all sessions</a></strong></p><p><strong><a href="https://planetscale.com/docs/security/access-control#revoke-member-tokens">Read more about revoking member tokens</a></strong></p>]]></content>
        <summary><![CDATA[If you lose a device, you can now revoke all of your sessions from your account settings. This signs you out of PlanetScale in every other browser and revokes your pscale CLI logins and the OAuth applications you authorized, such as MCP clients. The organization service tokens are not affected.]]></summary>
      </entry>
    
      <entry>
        <title>Authenticate to the PlanetScale API from Buildkite with OpenID Connect</title>
        <link href="https://planetscale.com/changelog/oidc-authentication-buildkite" />
        <id>https://planetscale.com/changelog/oidc-authentication-buildkite</id>
        <published>2026-11-16T20:42:23.000Z</published>
        <updated>2026-11-16T20:42:23.000Z</updated>
        <content type="html"><![CDATA[<p>You can now authenticate to the PlanetScale API from Buildkite pipelines using OpenID Connect (OIDC). A pipeline step exchanges its Buildkite OIDC token for a short-lived service token, so you no longer need to store long-lived PlanetScale credentials in your Buildkite secrets.</p><p>Create a Buildkite trust policy in the <a href="https://app.planetscale.com/~/settings/oidc">dashboard</a> for your Buildkite organization and pipeline, then request a token with <code>buildkite-agent oidc request-token</code> and exchange it with the PlanetScale API.</p><p><strong><a href="https://planetscale.com/docs/api/oidc#buildkite">Read more</a></strong></p>]]></content>
        <summary><![CDATA[You can now authenticate to the PlanetScale API from Buildkite pipelines using OpenID Connect (OIDC).A pipeline step exchanges its Buildkite OIDC token for a short-lived service token, so you no longer need to store long-lived PlanetScale credentials in your Buildkite secrets.]]></summary>
      </entry>
    
      <entry>
        <title>Postgres security fixes for Neki</title>
        <link href="https://planetscale.com/changelog/neki-postgres-security-fixes" />
        <id>https://planetscale.com/changelog/neki-postgres-security-fixes</id>
        <published>2026-11-13T16:30:00.000Z</published>
        <updated>2026-11-13T16:30:00.000Z</updated>
        <content type="html"><![CDATA[<p>Neki now runs Postgres 18.7, the latest upstream minor release, which fixes 52 security vulnerabilities. We&#x27;ve already upgraded existing Neki databases, and new Neki databases start on 18.7.</p><p><strong><a href="https://planetscale.com/docs/neki/cluster-configuration/maintenance-windows">Neki maintenance windows</a></strong> or read the upstream <a href="https://www.postgresql.org/docs/release/18.7/">18.7 release notes</a>.</p>]]></content>
        <summary><![CDATA[Neki now runs Postgres 18.7, the latest upstream minor release, which fixes 52 security vulnerabilities. We've already upgraded existing Neki databases, and new Neki databases start on 18.7.]]></summary>
      </entry>
    
      <entry>
        <title>Postgres minor version updates with security fixes</title>
        <link href="https://planetscale.com/changelog/postgres-minor-version-security-updates" />
        <id>https://planetscale.com/changelog/postgres-minor-version-security-updates</id>
        <published>2026-11-13T01:38:19.000Z</published>
        <updated>2026-11-13T01:38:19.000Z</updated>
        <content type="html"><![CDATA[<p>New PlanetScale Postgres databases now use 17.12 and 18.7, the latest upstream minor releases, which include security fixes. Existing databases will be upgraded to these versions over the next few days.</p><p><strong><a href="https://planetscale.com/docs/postgres/cluster-configuration/versions">See supported versions</a></strong> or read the upstream release notes for <a href="https://www.postgresql.org/docs/release/17.12/">17.12</a> and <a href="https://www.postgresql.org/docs/release/18.7/">18.7</a>.</p>]]></content>
        <summary><![CDATA[New PlanetScale Postgres databases now use 17.12 and 18.7, the latest upstream minor releases, which include security fixes. Existing databases will be upgraded to these versions over the next few days.]]></summary>
      </entry>
    
      <entry>
        <title>Manage OIDC trusts from the CLI</title>
        <link href="https://planetscale.com/changelog/oidc-trust-cli-commands" />
        <id>https://planetscale.com/changelog/oidc-trust-cli-commands</id>
        <published>2026-11-12T20:30:00.000Z</published>
        <updated>2026-11-12T20:30:00.000Z</updated>
        <content type="html"><![CDATA[<p>We&#x27;ve added <code>pscale oidc-trust</code> to the CLI. You can now create, list, show, update, and delete OIDC trusts from your terminal.</p><pre data-language="bash">pscale oidc-trust providers list --org acme
pscale oidc-trust create --org acme --name &quot;Deploy from main&quot; \
  --provider github_actions --max-ttl 900 \
  --condition repository_id=123456 --condition repository_owner_id=7890 \
  --database-access mydb:read_branch
</pre><p>Use <code>providers list</code> and <code>providers show</code> to see the supported providers and the claims in their tokens.</p><p><strong><a href="https://planetscale.com/docs/cli/oidc-trust">Read the CLI oidc-trust docs</a></strong></p>]]></content>
        <summary><![CDATA[We've added pscale oidc-trust to the CLI. You can now create, list, show, update, and delete OIDC trusts from your terminal.pscale oidc-trust providers list --org acme]]></summary>
      </entry>
    
      <entry>
        <title>Cmd-K palette for quick navigation and actions</title>
        <link href="https://planetscale.com/changelog/cmd-k-palette" />
        <id>https://planetscale.com/changelog/cmd-k-palette</id>
        <published>2026-11-12T14:00:00.000Z</published>
        <updated>2026-11-12T14:00:00.000Z</updated>
        <content type="html"><![CDATA[<p>We&#x27;ve added a command palette to the dashboard. Press Cmd-K on macOS (or Ctrl-K on Windows and Linux) to quickly jump to Insights sections, cluster configuration pages, and settings without clicking through menus.</p><p>You can also switch between organizations, databases, and branches directly from the palette. This makes navigating large setups much faster, especially when you&#x27;re working across multiple databases.</p>]]></content>
        <summary><![CDATA[We've added a command palette to the dashboard. Press Cmd-K on macOS (or Ctrl-K on Windows and Linux) to quickly jump to Insights sections, cluster configuration pages, and settings without clicking through menus.]]></summary>
      </entry>
    
      <entry>
        <title>Passkeys and security keys</title>
        <link href="https://planetscale.com/changelog/passkeys-and-security-keys" />
        <id>https://planetscale.com/changelog/passkeys-and-security-keys</id>
        <published>2026-11-09T20:29:00.000Z</published>
        <updated>2026-11-09T20:29:00.000Z</updated>
        <content type="html"><![CDATA[<p>You can now add a passkey or a hardware security key from your <a href="https://app.planetscale.com/account">account settings</a>. The next time you sign in, you can use it instead of a code from your authenticator app.</p><p>If your organization has SSO enabled, configuration remains with your SSO provider.</p><p><strong><a href="https://planetscale.com/docs/security/multi-factor-authentication">Read more</a></strong></p>]]></content>
        <summary><![CDATA[You can now add a passkey or a hardware security key from your account settings. The next time you sign in, you can use it instead of a code from your authenticator app.]]></summary>
      </entry>
    
      <entry>
        <title>Switch from GitHub sign-in to email and password</title>
        <link href="https://planetscale.com/changelog/disconnect-github-sign-in" />
        <id>https://planetscale.com/changelog/disconnect-github-sign-in</id>
        <published>2026-11-09T20:00:00.000Z</published>
        <updated>2026-11-09T20:00:00.000Z</updated>
        <content type="html"><![CDATA[<p>If you sign in to PlanetScale with GitHub, you can now switch your account to email and password sign-in. In your <a href="https://app.planetscale.com/settings/account">account settings</a>, select <strong>Disconnect GitHub</strong>, confirm on GitHub, then set a password.</p><p>After you disconnect, signing in with GitHub stops working for your account and you are signed out of PlanetScale in your other browsers.</p><p><strong><a href="https://planetscale.com/docs/security/authentication-methods#switch-to-email-and-password">Read more</a></strong></p>]]></content>
        <summary><![CDATA[If you sign in to PlanetScale with GitHub, you can now switch your account to email and password sign-in. In your account settings, select Disconnect GitHub, confirm on GitHub, then set a password.]]></summary>
      </entry>
    
      <entry>
        <title>Authenticate to the PlanetScale API with OpenID Connect</title>
        <link href="https://planetscale.com/changelog/oidc-authentication-github-actions-depot-ci" />
        <id>https://planetscale.com/changelog/oidc-authentication-github-actions-depot-ci</id>
        <published>2026-11-05T20:30:00.000Z</published>
        <updated>2026-11-05T20:30:00.000Z</updated>
        <content type="html"><![CDATA[<p>You can now authenticate to the PlanetScale API from GitHub Actions and Depot CI using OpenID Connect (OIDC). Workflows will exchange their OIDC token for a short-lived service token, so you no longer need to store long-lived credentials in your CI secrets.</p><p>Organization admins create a trust policy in the <a href="https://app.planetscale.com/~/settings/oidc">dashboard</a> that defines the claims a workflow must present, such as a repository or branch, along with the access to grant and how long the service token lasts. The new <a href="https://github.com/planetscale/auth-action"><code>planetscale/auth-action</code></a> handles the exchange for you in a workflow job with the <code>id-token: write</code> permission.</p><p><strong><a href="https://planetscale.com/docs/api/oidc">Read more</a></strong></p>]]></content>
        <summary><![CDATA[You can now authenticate to the PlanetScale API from GitHub Actions and Depot CI using OpenID Connect (OIDC).Workflows will exchange their OIDC token for a short-lived service token, so you no longer need to store long-lived credentials in your CI secrets.]]></summary>
      </entry>
    
      <entry>
        <title>MCP server: Dedicated egress IPs</title>
        <link href="https://planetscale.com/changelog/mcp-server-dedicated-egress-ips" />
        <id>https://planetscale.com/changelog/mcp-server-dedicated-egress-ips</id>
        <published>2026-11-05T18:00:00.000Z</published>
        <updated>2026-11-05T18:00:00.000Z</updated>
        <content type="html"><![CDATA[<p>The <a href="https://planetscale.com/docs/mcp-server">PlanetScale MCP server</a> now runs on a new platform, and its database queries leave from four dedicated IP addresses:</p><ul><li><code>104.28.1.231</code></li><li><code>104.28.1.232</code></li><li><code>104.28.1.233</code></li><li><code>104.28.1.234</code></li></ul><p>If your Postgres database uses IP restrictions, add all four addresses so MCP queries can connect. Vitess databases need no changes, since the MCP server restricts its own short-lived passwords to these addresses.</p><p>Existing sign-ins keep working. If you run into issues, re-authenticate the MCP server in your client.</p><p><strong><a href="https://planetscale.com/docs/mcp-server">MCP server docs</a></strong> · <strong><a href="https://planetscale.com/docs/postgres/connecting/ip-restrictions">IP restrictions</a></strong></p>]]></content>
        <summary><![CDATA[The PlanetScale MCP server now runs on a new platform, and its database queries leave from four dedicated IP addresses:]]></summary>
      </entry>
    
      <entry>
        <title>Manage Vitess parameters with Terraform</title>
        <link href="https://planetscale.com/changelog/vitess-parameters-terraform" />
        <id>https://planetscale.com/changelog/vitess-parameters-terraform</id>
        <published>2026-11-05T01:22:00.000Z</published>
        <updated>2026-11-05T01:22:00.000Z</updated>
        <content type="html"><![CDATA[<p>Manage Vitess parameters with v1.18.0 of the PlanetScale Terraform provider. Set VTGate parameters in <code>planetscale_vitess_branch</code>, and VTTablet and MySQL parameters in <code>planetscale_vitess_keyspace</code>.</p><p><strong><a href="https://github.com/planetscale/terraform-provider-planetscale/blob/main/docs/resources/vitess_branch.md">Terraform provider docs for planetscale_vitess_branch</a></strong> · <strong><a href="https://github.com/planetscale/terraform-provider-planetscale/blob/main/docs/resources/vitess_keyspace.md">Terraform provider docs for planetscale_vitess_keyspace</a></strong></p>]]></content>
        <summary><![CDATA[Manage Vitess parameters with v1.18.0 of the PlanetScale Terraform provider. Set VTGate parameters in planetscale_vitess_branch, and VTTablet and MySQL parameters in planetscale_vitess_keyspace.]]></summary>
      </entry>
    
      <entry>
        <title>MCP server: Send feedback and questions to PlanetScale</title>
        <link href="https://planetscale.com/changelog/mcp-feedback-and-questions" />
        <id>https://planetscale.com/changelog/mcp-feedback-and-questions</id>
        <published>2026-11-03T23:30:00.000Z</published>
        <updated>2026-11-03T23:30:00.000Z</updated>
        <content type="html"><![CDATA[<p>We&#x27;ve added two tools to the <a href="https://planetscale.com/docs/mcp-server">PlanetScale MCP server</a> that let your AI agent tell us what got in its way.</p><ul><li><code>planetscale_submit_feedback</code>: report a problem, such as a wrong result, a confusing error, a documentation gap, or a missing tool.</li><li><code>planetscale_ask_question</code>: record a question the docs and tools couldn&#x27;t answer, so we know where to fill the gap.</li></ul><p>Your agent will send a short note, along with the tool, organization, and database it&#x27;s about. Each submission goes straight to the PlanetScale team with your PlanetScale user ID and email address, so we can follow up.</p><p>Try it out with prompts like:</p><ul><li>&quot;Tell PlanetScale that <code>get_insights</code> was slow on my production branch&quot;</li><li>&quot;Ask PlanetScale whether a branch&#x27;s replicas can use a different cluster size&quot;</li></ul><p><strong><a href="https://planetscale.com/docs/mcp-server">MCP server docs</a></strong></p>]]></content>
        <summary><![CDATA[We've added two tools to the PlanetScale MCP server that let your AI agent tell us what got in its way.]]></summary>
      </entry>
    
      <entry>
        <title>Emergency backups for Vitess databases</title>
        <link href="https://planetscale.com/changelog/vitess-emergency-backups" />
        <id>https://planetscale.com/changelog/vitess-emergency-backups</id>
        <published>2026-11-03T00:00:00.000Z</published>
        <updated>2026-11-03T00:00:00.000Z</updated>
        <content type="html"><![CDATA[<p>We&#x27;ve added emergency backups to Vitess databases. An emergency backup will copy data directly from your running database instead of starting from the previous backup. This ensures you can get a fresh backup right away, even when regular backups are failing.</p><p>On production branches, you can choose to copy from the primary or from a replica. Copying from a replica reduces the load on your primary. Emergency backups are retained, billed, and restored the same way as manual backups.</p><p>You can create one from the <strong>Backups</strong> page in the dashboard, the API, or the CLI with <code>pscale backup create --emergency --emergency-source primary|replica</code>.</p><p><strong><a href="https://planetscale.com/docs/vitess/backups#emergency-backups">Read more</a></strong></p>]]></content>
        <summary><![CDATA[We've added emergency backups to Vitess databases. An emergency backup will copy data directly from your running database instead of starting from the previous backup. This ensures you can get a fresh backup right away, even when regular backups are failing.]]></summary>
      </entry>
    
      <entry>
        <title>Choose when Postgres maintenance restarts your database</title>
        <link href="https://planetscale.com/changelog/postgres-maintenance-notice-and-rescheduling" />
        <id>https://planetscale.com/changelog/postgres-maintenance-notice-and-rescheduling</id>
        <published>2026-10-29T17:00:00.000Z</published>
        <updated>2026-10-29T17:00:00.000Z</updated>
        <content type="html"><![CDATA[<p>Every Postgres database now has a maintenance window. Your database only restarts in its window when maintenance needs a restart, such as an image update. Your database administrators get an email at least 7 days ahead and again 3 days before. If the time doesn&#x27;t work, you can move it to any upcoming window before its deadline, up to 3 times.</p><p>The rest of the time, your window will only run routine maintenance, which doesn&#x27;t restart Postgres.</p><p>You can change your window and reschedule maintenance from the dashboard or through the API.</p><p><picture class="block"><source media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" srcSet="https://planetscale-images.imgix.net/assets/postgres-maintenance-notice-and-rescheduling-C-QC0V4p.png?auto=compress%2Cformat"><img alt="Settings Maintenance page showing each production branch&#x27;s weekly maintenance window" src="https://planetscale-images.imgix.net/assets/postgres-maintenance-notice-and-rescheduling-C-QC0V4p.png?auto=compress%2Cformat" width="3093" height="1720" loading="lazy"></picture></p><p><strong><a href="https://planetscale.com/docs/postgres/cluster-configuration/maintenance-windows">Read more</a></strong></p>]]></content>
        <summary><![CDATA[Every Postgres database now has a maintenance window.Your database only restarts in its window when maintenance needs a restart, such as an image update. Your database administrators get an email at least 7 days ahead and again 3 days before. If the time doesn't work, you can move it to any upcoming window before its deadline, up to 3 times.]]></summary>
      </entry>
    
      <entry>
        <title>Manage Postgres storage configuration in Terraform</title>
        <link href="https://planetscale.com/changelog/postgres-storage-configuration-terraform" />
        <id>https://planetscale.com/changelog/postgres-storage-configuration-terraform</id>
        <published>2026-10-29T16:02:35.000Z</published>
        <updated>2026-10-29T16:02:35.000Z</updated>
        <content type="html"><![CDATA[<p>Manage Postgres storage configuration with v1.16.0 of the PlanetScale Terraform provider. Configure minimum and maximum storage, autoscaling, IOPS, and throughput in the <code>planetscale_postgres_branch</code> resource.</p><p>This keeps storage settings in version-controlled infrastructure code and lets Terraform detect configuration drift.</p><p><strong><a href="https://github.com/planetscale/terraform-provider-planetscale/blob/main/docs/resources/postgres_branch.md">Read more in the Terraform provider docs</a></strong></p>]]></content>
        <summary><![CDATA[Manage Postgres storage configuration with v1.16.0 of the PlanetScale Terraform provider. Configure minimum and maximum storage, autoscaling, IOPS, and throughput in the planetscale_postgres_branch resource.]]></summary>
      </entry>
    
      <entry>
        <title>Egress bandwidth email notifications</title>
        <link href="https://planetscale.com/changelog/egress-bandwidth-email-notifications" />
        <id>https://planetscale.com/changelog/egress-bandwidth-email-notifications</id>
        <published>2026-10-27T18:50:00.000Z</published>
        <updated>2026-10-27T18:50:00.000Z</updated>
        <content type="html"><![CDATA[<p>We&#x27;ve enabled email notifications for Postgres and Neki databases to inform you when we detect higher than usual public network egress.</p><p><strong><a href="https://planetscale.com/docs/postgres/pricing#network-data-transfer">Postgres network egress</a></strong></p><p><strong><a href="https://planetscale.com/docs/neki/pricing#public-traffic">Neki network transfer</a></strong></p>]]></content>
        <summary><![CDATA[We've enabled email notifications for Postgres and Neki databases to inform you when we detect higher than usual public network egress.]]></summary>
      </entry>
    
      <entry>
        <title>Service tokens include the last used IP, location, and network operator</title>
        <link href="https://planetscale.com/changelog/service-token-last-used-ip" />
        <id>https://planetscale.com/changelog/service-token-last-used-ip</id>
        <published>2026-10-26T18:51:00.000Z</published>
        <updated>2026-10-26T18:51:00.000Z</updated>
        <content type="html"><![CDATA[<p>Service tokens will now show the IP address they were last used from, along with the location and the organization that runs that network, such as an ISP or cloud provider. You&#x27;ll find this in the dashboard, the API, and the CLI. This gives more visibility into how your tokens are being used.</p><p>In addition to the service token update, audit logs in the UI and API now also include the organization that runs the network behind the IP.</p><p><strong><a href="https://planetscale.com/docs/api/service-tokens">Service tokens</a></strong> · <strong><a href="https://planetscale.com/docs/cli/service-token">CLI</a></strong> · <strong><a href="https://planetscale.com/docs/security/audit-log">Audit log</a></strong></p>]]></content>
        <summary><![CDATA[Service tokens will now show the IP address they were last used from, along with the location and the organization that runs that network, such as an ISP or cloud provider. You'll find this in the dashboard, the API, and the CLI. This gives more visibility into how your tokens are being used.]]></summary>
      </entry>
    
      <entry>
        <title>More Vitess operations in the CLI and API</title>
        <link href="https://planetscale.com/changelog/vitess-vtctl-operations" />
        <id>https://planetscale.com/changelog/vitess-vtctl-operations</id>
        <published>2026-10-24T22:15:00.000Z</published>
        <updated>2026-10-24T22:15:00.000Z</updated>
        <content type="html"><![CDATA[<p>We&#x27;ve opened a wider set of Vitess operations on PlanetScale. Alongside <a href="https://planetscale.com/docs/cli/move-tables">MoveTables</a>, you can now run <a href="https://planetscale.com/docs/cli/materialize">Materialize</a>, <a href="https://planetscale.com/docs/cli/lookup-vindex">Lookup Vindex</a>, <a href="https://planetscale.com/docs/cli/vdiff">VDiff</a>, and <a href="https://planetscale.com/docs/cli/planned-reparent-shard">PlannedReparentShard</a> from <code>pscale branch vtctl</code> (alias <code>vtctld</code>), plus helpers like listing tablets and updating shard tablet controls.</p><p>These map closely to the matching Vitess <code>vtctldclient</code> commands.</p><p><strong><a href="https://planetscale.com/docs/cli/vtctl">vtctl overview</a></strong> · <strong><a href="https://planetscale.com/docs/vitess/scaling/workflows">Workflows</a></strong></p>]]></content>
        <summary><![CDATA[We've opened a wider set of Vitess operations on PlanetScale. Alongside MoveTables, you can now run Materialize, Lookup Vindex, VDiff, and PlannedReparentShard from pscale branch vtctl (alias vtctld), plus helpers like listing tablets and updating shard tablet controls.]]></summary>
      </entry>
    
      <entry>
        <title>Vitess Materialize workflows in the dashboard</title>
        <link href="https://planetscale.com/changelog/materialize-workflows-dashboard" />
        <id>https://planetscale.com/changelog/materialize-workflows-dashboard</id>
        <published>2026-10-23T16:00:00.000Z</published>
        <updated>2026-10-23T16:00:00.000Z</updated>
        <content type="html"><![CDATA[<p>The <strong>Workflows</strong> page for a Vitess branch now lists Materialize workflows alongside MoveTables workflows, with the type shown for each one.</p><p>Open a Materialize workflow to see its stream states, replication lag, and the tables it materializes with the query that feeds each one. Creating, starting, stopping, and cancelling Materialize workflows stays in the CLI with <code>pscale branch vtctld materialize</code>.</p><p><strong><a href="https://planetscale.com/docs/vitess/scaling/workflows">Read more</a></strong></p>]]></content>
        <summary><![CDATA[The Workflows page for a Vitess branch now lists Materialize workflows alongside MoveTables workflows, with the type shown for each one.]]></summary>
      </entry>
    
      <entry>
        <title>Live connections for Neki</title>
        <link href="https://planetscale.com/changelog/neki-live-connections" />
        <id>https://planetscale.com/changelog/neki-live-connections</id>
        <published>2026-10-22T18:00:00.000Z</published>
        <updated>2026-10-22T18:00:00.000Z</updated>
        <content type="html"><![CDATA[<p>You can now see live connections to your Neki routers in the dashboard under <strong>Connections</strong>, or with <code>pscale branch connections show</code> and <code>pscale branch connections top</code>.</p><p>From the dashboard or the CLI, you can cancel a router session&#x27;s running query or terminate the session. Cancelling stops the statement and keeps the connection open. Terminating closes the client&#x27;s connection to the router and rolls back any open transaction, the same as if the client had disconnected.</p><p>Connections only shows router sessions. It doesn&#x27;t show the connections between routers and each shard&#x27;s Postgres instances.</p><p><strong><a href="https://planetscale.com/docs/neki/monitoring/connections">Read more</a></strong> · <strong><a href="https://planetscale.com/docs/cli/connections">CLI reference</a></strong></p>]]></content>
        <summary><![CDATA[You can now see live connections to your Neki routers in the dashboard under Connections, or with pscale branch connections show and pscale branch connections top.]]></summary>
      </entry>
    
    </feed>