From 6a1982089c2436028fcb48de2e7c609c2ecf4e08 Mon Sep 17 00:00:00 2001
From: Brian <briantgbtheonly@gmail.com>
Date: Sun, 28 Sep 2025 16:10:58 -0400
Subject: [PATCH] add tip to migration docs around lock_timeout

---
 .../content/guides/deployment/database-migrations.mdx  | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/apps/docs/content/guides/deployment/database-migrations.mdx b/apps/docs/content/guides/deployment/database-migrations.mdx
index c3816014366..5587e784f7f 100644
--- a/apps/docs/content/guides/deployment/database-migrations.mdx
+++ b/apps/docs/content/guides/deployment/database-migrations.mdx
@@ -15,6 +15,16 @@ For this guide, we'll create a table called `employees` and see how we can make
 
 You will need to [install](/docs/guides/local-development#quickstart) the Supabase CLI and start the local development stack.
 
+<Admonition type="tip">
+
+If a lock timeout error occurs, in your migration file, consider increasing you [`lock_timeout`](https://postgresqlco.nf/doc/en/param/lock_timeout/) setting:
+
+```sql
+SET lock_timeout = '2min';
+```
+
+</Admonition>
+
 <StepHikeCompact>
 
   <StepHikeCompact.Step step={1}>