[GH-ISSUE #91] A lot of idle connections after fast backup #71

Open
opened 2026-02-26 21:34:17 +03:00 by kerem · 0 comments
Owner

Originally created by @TristisOris on GitHub (Feb 7, 2025).
Original GitHub issue: https://github.com/eduardolat/pgbackweb/issues/91

We do backup for 2 db, huge and small.

Image

After small one, we got a lot of idle coneections. Looks like backup done too fast to close them correctly. But zero idle after huge one, that most weird part.

Image

Image

Image

as far as i know, it possible to specify timeout for pgdump, like
pg_dump -d 'host=... port=... dbname=... user=... keepalives_idle=300' -f dumpfile

On database side we can play with idle_session_timeout.

Originally created by @TristisOris on GitHub (Feb 7, 2025). Original GitHub issue: https://github.com/eduardolat/pgbackweb/issues/91 We do backup for 2 db, huge and small. ![Image](https://github.com/user-attachments/assets/9417a966-57f6-41fd-8b54-0309c6fa50af) After small one, we got a lot of idle coneections. Looks like backup done too fast to close them correctly. But zero idle after huge one, that most weird part. ![Image](https://github.com/user-attachments/assets/a209ae98-f02e-488b-9d19-7b018384df9c) ![Image](https://github.com/user-attachments/assets/6afadf36-7404-4ce1-bce6-e39fd6f1eaac) ![Image](https://github.com/user-attachments/assets/575ec85b-2096-428e-a91c-813fbda605d2) as far as i know, it possible to specify timeout for pgdump, like `pg_dump -d 'host=... port=... dbname=... user=... keepalives_idle=300' -f dumpfile` On database side we can play with `idle_session_timeout`.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/pgbackweb#71
No description provided.