mirror of
https://github.com/eduardolat/pgbackweb.git
synced 2026-04-25 05:35:57 +03:00
[GH-ISSUE #91] A lot of idle connections after fast backup #71
Labels
No labels
bug
confirmed next step
duplicate
enhancement
help wanted
in progress
in progress
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/pgbackweb#71
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
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.
as far as i know, it possible to specify timeout for pgdump, like
pg_dump -d 'host=... port=... dbname=... user=... keepalives_idle=300' -f dumpfileOn database side we can play with
idle_session_timeout.