Starting November 1, 2026, at 02:00 a.m. local time, unpatched Cloud SQL for PostgreSQL

## Announcement Announcement Starting November 1, 2026, at 02:00 a.m. local time, unpatched Cloud SQL for PostgreSQL instances that evaluate certain local Canadian time zones (across Alberta, British Columbia, Manitoba, and Northwest Territories) will lag by one hour because the instances still follow the autumn fall back schedule. Stored timestamp data isn't modified. **What should I do?** Before November 1, 2026, do one of the following fixes: * **Apply self-service maintenance (Recommended):** If your applications rely on database functions to calculate, schedule, or display times in these Canadian time zones (such as Calgary, Edmonton, Vancouver, or Winnipeg), then update your instances to the latest maintenance release using the Google Cloud console or the gcloud CLI. Updated time zone rules that reflect permanent standard daylight offsets across Alberta, British Columbia, Manitoba, and Northwest Territories are supported in Cloud SQL for PostgreSQL [maintenance release \*.R20260712.01\_44 or later](https://cloud.google.com/sql/docs/postgres/maintenance-changelog). For more information, see[Perform self-service maintenance](https://cloud.google.com/sql/docs/postgres/self-service-maintenance). * **Database configuration stopgap:** If your organization can't restart instances before November 1, 2026, then you can set your database session time zone without downtime to an anchor zone. ALTER DATABASE database_name SET timezone TO 'anchor_zone'; Replace the following: * `database_name`: the name of your database. * `anchor_zone`: the anchor zone to use as the time zone for your database. Specify an anchor zone that operates on a permanent offset. For example, `'America/Regina'` for Alberta and Northwest Territories (UTC-6), `'America/Whitehorse'` for British Columbia (UTC-7), or`'America/Coral_Harbour'` for Manitoba (UTC-5).