1---
2title: Use Prepared Statements Correctly with Pooling
3impact: HIGH
4impactDescription: Avoid prepared statement conflicts in pooled environments
5tags: prepared-statements, connection-pooling, transaction-mode
6---
7 
8## Use Prepared Statements Correctly with Pooling
9 
10Prepared statements are tied to individual database connections. In transaction-mode pooling, connections are shared, causing conflicts.
11 
12**Incorrect (named prepared statements with transaction pooling):**
13 
14```sql
15-- Named prepared statement
16prepare get_user as select * from users where id = $1;
17 
18-- In transaction mode pooling, next request may get different connection
19execute get_user(123);
20-- ERROR: prepared statement "get_user" does not exist
21```
22 
23**Correct (use unnamed statements or session mode):**
24 
25```sql
26-- Option 1: Use unnamed prepared statements (most ORMs do this automatically)
27-- The query is prepared and executed in a single protocol message
28 
29-- Option 2: Deallocate after use in transaction mode
30prepare get_user as select * from users where id = $1;
31execute get_user(123);
32deallocate get_user;
33 
34-- Option 3: Use session mode pooling (port 5432 vs 6543)
35-- Connection is held for entire session, prepared statements persist
36```
37 
38Check your driver settings:
39 
40```sql
41-- Many drivers use prepared statements by default
42-- Node.js pg: { prepare: false } to disable
43-- JDBC: prepareThreshold=0 to disable
44```
45 
46Reference: [Prepared Statements with Pooling](https://supabase.com/docs/guides/database/connecting-to-postgres#connection-pool-modes)
47