mirror of
https://github.com/eduardolat/pgbackweb.git
synced 2026-04-25 05:35:57 +03:00
[GH-ISSUE #129] Allow custom cron interval for health checks #107
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#107
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 @Dopixel on GitHub (Jul 30, 2025).
Original GitHub issue: https://github.com/eduardolat/pgbackweb/issues/129
Originally assigned to: @eduardolat on GitHub.
Hi there 👋
First of all, thank you so much for this amazing tool — it’s incredibly helpful for managing my clients' PostgreSQL backups.
I’m currently using a serverless PostgreSQL provider (neon.tech), and I’ve noticed that my billing increased almost 8x since setting up PgBackWeb 😅
After investigating, it appears this is caused by the health checks running every 10 minutes, which keeps the database constantly awake and triggers serverless billing.
Would you consider supporting this kind of serverless use case by allowing the user to customize the health check interval?
For example:
PBW_DB_HEALTHCHECK_CRONcmd/app/init_schedule.goor config-driven cron setup)For now, I’ve had to temporarily stop using PgBackWeb to avoid unnecessary billing while waiting for a solution 🙏
Thank you again for your hard work — looking forward to seeing this tool evolve!
@eduardolat commented on GitHub (Aug 8, 2025):
You're welcome and thanks for using pg back web and of course let me implement this when I have some free time.
@Dopixel commented on GitHub (Aug 8, 2025):
Thank you 🙏