## TL;DR

Set poolMode to transaction so connections are released after each transaction. Create a ConnectionPool resource for Aiven Postgres and use the generated pool URI for application traffic, keeping the direct service URI for migrations.

## Steps

1. Create a ConnectionPool resource for Aiven Postgres and use the generated pool URI for application traffic, keeping the direct service URI for migrations. Set poolMode to transaction so connections are released after each transaction. Size poolSize for your plan; the Kubernetes operator caps it at 1000.

## When to use

You are seeing this: Size poolSize for your plan; the Kubernetes operator caps it at 1000. Use this skill when you run into "Aiven Postgres apps should use the PgBouncer pool URI, not direct".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.