| From: | Raj <rajeshkumar(dot)dba09(at)gmail(dot)com> |
|---|---|
| To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Pgbouncer |
| Date: | 2025-09-11 13:31:26 |
| Message-ID: | CAJk5Atanc-d4xg_3UxbTybvNmPfb593WAhLFqjAWEUhm5cYQDQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
We are migrating from oracle.to postgres and its done.
Now as a DBA, to improve performance say idle connecting handling or
anything, if I want to recommend pgbouncer to the team, what's the
compelling reason would it be?
I may ask them to handle connections from application end and they may say
ok but we still.may see idle connections are not closed.
So, at point and for what compelling reason I should tell my manager, we
must go-ahead and use etc.
We use pg17 and in postgres itself I know idle_session_timeount,
transaction_timeout, statement_timeout. Is this enough? Will it abruptly
kill queries and if so, isn't it bad?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hubert depesz lubaczewski | 2025-09-11 13:55:22 | Re: Pgbouncer |
| Previous Message | Laurenz Albe | 2025-09-10 21:35:45 | Re: values of column source in pg_settings |