---
title: "Discussion on \"Why DATE(updated_at) Broke Timezones and Killed PostgreSQL Index Performance\" | Hashnode"
description: "Discussion on \"Why DATE(updated_at) Broke Timezones and Killed PostgreSQL Index Performance\". A real-world deep-dive into how a single SQL wrapper caused wrong dates for international users and made indexes completely useless — and the SARGable fix that resolved both."
url: "https://hashnode.com/posts/why-date-updated-at-broke-timezones-and-killed-postgresql-index-performance/69e697e2c9501dd01036ca18"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why DATE(updated\_at) Broke Timezones and Killed PostgreSQL Index Performance](https://shantanubadmanji.hashnode.dev/why-date-updated-at-broke-timezones-and-killed-postgresql-index-performance?utm_source=hashnode&utm_medium=feed)

A real-world deep-dive into how a single SQL wrapper caused wrong dates for international users and made indexes completely useless — and the SARGable fix that resolved both.

Apr 20 · 7 min read · shantanubadmanji.hashnode.dev  
Read the article

-   [#postgresql](https://hashnode.com/tag/postgresql)
-   [#backend](https://hashnode.com/tag/backend)
-   [#performance-optimization](https://hashnode.com/tag/performance-optimization)
-   [#timezone](https://hashnode.com/tag/timezone)

## Written by

[Shantanu Badmanji](https://hashnode.com/@ShantanuBadmanji)

@ShantanuBadmanji

  
[View profile](https://hashnode.com/@ShantanuBadmanji)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
