From 89f49630c4cedad4c7c9ab364906b078b585c802 Mon Sep 17 00:00:00 2001 From: Raja Yogan Date: Fri, 17 Oct 2025 02:53:34 +0530 Subject: [PATCH] Update _use-case-transport-geolocation.md Hinting about the tuple decompression limit error and how to set it to zero. Signed-off-by: Raja Yogan --- _partials/_use-case-transport-geolocation.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/_partials/_use-case-transport-geolocation.md b/_partials/_use-case-transport-geolocation.md index e92679180a..e9ef5b9f3d 100644 --- a/_partials/_use-case-transport-geolocation.md +++ b/_partials/_use-case-transport-geolocation.md @@ -26,7 +26,20 @@ data by time and location. UPDATE rides SET pickup_geom = ST_Transform(ST_SetSRID(ST_MakePoint(pickup_longitude,pickup_latitude),4326),2163), dropoff_geom = ST_Transform(ST_SetSRID(ST_MakePoint(dropoff_longitude,dropoff_latitude),4326),2163); ``` - This updates 10,906,860 rows of data on both columns, it takes a while. Coffee is your friend. + This updates 10,906,860 rows of data on both columns, it takes a while. Coffee is your friend. + + You might run into this error while the update happens + + `Error: tuple decompression limit exceeded by operation + Error Code: 53400 + Details: current limit: 100000, tuples decompressed: 10906860 + Hint: Consider increasing timescaledb.max_tuples_decompressed_per_dml_transaction or set to 0 (unlimited).` + + To fix this, use + + ```sql + SET timescaledb.max_tuples_decompressed_per_dml_transaction TO 0; + ```