From 6170e2645bc191962913d3cbc31503e8ea447be2 Mon Sep 17 00:00:00 2001
From: Andrew Kane <andrew@ankane.org>
Date: Mon, 28 Oct 2024 22:44:44 -0700
Subject: [PATCH] Updated readme [skip ci]

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 9984146..1b0b562 100644
--- a/README.md
+++ b/README.md
@@ -442,7 +442,7 @@ CREATE INDEX ON items (category_id);
 For multiple columns, consider a [multicolumn index](https://www.postgresql.org/docs/current/indexes-multicolumn.html).
 
 ```sql
-CREATE INDEX ON items (store_id, category_id);
+CREATE INDEX ON items (location_id, category_id);
 ```
 
 Exact indexes work well for conditions that match a lower percentage of rows. Otherwise, [approximate indexes](#indexing) can work better.