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.