Connection pooling with PgBouncer in Supabase - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the PgBouncer service in the Supabase configuration.

Supabase

services:
  - name: [1]
    image: pgbouncer/pgbouncer

Drag options to blanks, or click blank then click option'

Aredis

Bpostgres

Cpgbouncer

Dsupabase

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'postgres' instead of 'pgbouncer' as the service name.

Naming the service 'redis' or 'supabase' which are unrelated.

The PgBouncer service must be named pgbouncer to be recognized properly in the Supabase setup.

2fill in blank

medium

Complete the PgBouncer configuration to set the pool mode to transaction.

Supabase

[pgbouncer]
pool_mode = [1]

Drag options to blanks, or click blank then click option'

Asession

Bidle

Cstatement

Dtransaction

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'session' mode which holds connections longer.

Using 'statement' mode which is less common.

Using 'idle' which is not a valid pool mode.

The transaction pool mode allows PgBouncer to pool connections per transaction, improving efficiency.

3fill in blank

hard

Fix the error in the PgBouncer userlist configuration line.

Supabase

"userlist.txt" contains: "[1]"

Drag options to blanks, or click blank then click option'

A"admin" "password"

Badmin password

C""admin"" "password"

D'admin' 'password'

Attempts:

3 left

💡 Hint

Common Mistakes

Using single quotes instead of double quotes.

Adding extra double quotes inside the string.

Not quoting username and password.

The correct format for PgBouncer userlist is double quotes around username and password, like "admin" "password".

4fill in blank

hard

Fill both blanks to configure PgBouncer to listen on all interfaces and use port 6432.

Supabase

[pgbouncer]
listen_addr = [1]
listen_port = [2]

Drag options to blanks, or click blank then click option'

A"0.0.0.0"

B"127.0.0.1"

C6432

D5432

Attempts:

3 left

💡 Hint

Common Mistakes

Using 127.0.0.1 which restricts connections to localhost.

Using port 5432 which is PostgreSQL default, not PgBouncer's.

Setting listen_addr to "0.0.0.0" allows PgBouncer to accept connections from any IP. The default PgBouncer port is 6432.

5fill in blank

hard

Fill all three blanks to define a database entry in PgBouncer's config for Supabase.

Supabase

[databases]
[1] = host=[2] port=[3] dbname=supabase

Drag options to blanks, or click blank then click option'

Asupabase_db

Blocalhost

C5432

Dpgbouncer

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pgbouncer' as database key instead of 'supabase_db'.

Using PgBouncer port 6432 as the host port instead of PostgreSQL port 5432.

Using wrong host name.

The database name key should be supabase_db. The host is usually localhost when PgBouncer runs locally, and the PostgreSQL port is 5432.

Practice

1. What is the main purpose of using PgBouncer with a Supabase database?

easy

A. To increase the size of the database storage

B. To encrypt data between the app and database

C. To backup the database automatically

D. To reuse database connections and reduce load on the database

Solution

1. Step 1: Understand PgBouncer's role

   PgBouncer is a tool that manages and reuses database connections to avoid opening new ones repeatedly.

2. Step 2: Identify the benefit

   Reusing connections reduces the load on the database and improves app speed by avoiding connection overhead.

3. Final Answer:

   To reuse database connections and reduce load on the database -> Option D

4. Quick Check:

   Connection reuse = reduce load [OK]

Hint: PgBouncer saves time by reusing connections [OK]

Common Mistakes:

• Thinking PgBouncer encrypts data
• Confusing PgBouncer with backup tools
• Assuming it increases storage size

2. Which of the following is the correct way to specify the pooling mode in PgBouncer's configuration file?

easy

A. pool_mode = transaction

B. pooling-mode: session

C. poolMode = statement

D. pool_mode = connect

Solution

1. Step 1: Recall PgBouncer config syntax

   PgBouncer uses key = value format, with underscores in keys.

2. Step 2: Identify correct pooling mode syntax

   The correct key is pool_mode and valid values include transaction, session, and statement.

3. Final Answer:

   pool_mode = transaction -> Option A

4. Quick Check:

   Correct key and value format = pool_mode = transaction [OK]

Hint: Look for key = value with underscores [OK]

Common Mistakes:

• Using hyphens instead of underscores
• Capitalizing keys incorrectly
• Using invalid pooling mode names

3. Given this PgBouncer config snippet:

pool_mode = transaction
max_client_conn = 100
default_pool_size = 20

What happens when 50 clients connect simultaneously and each runs a short transaction?

medium

A. PgBouncer queues all clients until connections free up, causing delays

B. PgBouncer rejects connections after 20 clients because of pool size

C. PgBouncer allows all 50 clients to share 20 server connections efficiently

D. Each client gets a dedicated server connection, so 50 connections open

Solution

1. Step 1: Understand transaction pooling mode

   In transaction mode, PgBouncer assigns server connections only during active transactions, allowing reuse.

2. Step 2: Analyze connection limits

   default_pool_size = 20 means max 20 server connections per database/user pool, but clients can exceed this by sharing connections.

3. Final Answer:

   PgBouncer allows all 50 clients to share 20 server connections efficiently -> Option C

4. Quick Check:

   Transaction pooling shares connections = PgBouncer allows all 50 clients to share 20 server connections efficiently [OK]

Hint: Transaction pooling shares connections among clients [OK]

Common Mistakes:

• Assuming one client = one server connection
• Thinking pool size limits client connections
• Confusing session pooling with transaction pooling

4. You configured PgBouncer with pool_mode = transaction but your app experiences errors with prepared statements. What is the likely cause?

medium

A. PgBouncer does not support prepared statements in any mode

B. Transaction pooling reuses connections between clients, causing prepared statement conflicts

C. Transaction pooling is required for prepared statements to work

D. The max_client_conn setting is too low

Solution

1. Step 1: Understand transaction pooling behavior

   In transaction mode, PgBouncer assigns server connections only during transactions and reuses them for other clients after reset.

2. Step 2: Identify cause of errors

   Prepared statements fail because the connection state (including prepares) is reset (DISCARD ALL) between transactions/clients.

3. Final Answer:

   Transaction pooling reuses connections between clients, causing prepared statement conflicts -> Option B

4. Quick Check:

   Transaction pooling = resets between transactions [OK]

Hint: Transaction pooling reuses connections, watch prepared statement issues [OK]

Common Mistakes:

• Believing PgBouncer supports prepared statements in transaction mode
• Confusing transaction and session pooling effects
• Blaming max_client_conn for statement errors

5. You want to optimize a Supabase app with many short queries and avoid connection overhead. Which PgBouncer pooling mode should you choose and why?

hard

A. Transaction pooling, because it reuses connections only during transactions for best performance

B. Session pooling, because it keeps connections open for each client session

C. Statement pooling, because it assigns a connection per SQL statement

D. No pooling, to avoid any connection sharing issues

Solution

1. Step 1: Consider app query pattern

   Many short queries mean frequent connections and disconnections, so reusing connections efficiently is key.

2. Step 2: Evaluate pooling modes

   Transaction pooling assigns connections only during transactions, allowing reuse and reducing overhead without tying connections to sessions.

3. Step 3: Compare other modes

   Session pooling holds connections longer, increasing resource use; statement pooling is too strict and can cause errors; no pooling wastes resources.

4. Final Answer:

   Transaction pooling, because it reuses connections only during transactions for best performance -> Option A

5. Quick Check:

   Short queries + reuse = transaction pooling [OK]

Hint: Use transaction pooling for many short queries [OK]

Common Mistakes:

• Choosing session pooling for short queries
• Thinking statement pooling is best for performance
• Avoiding pooling altogether