3 ms·
David from Sentry here. We actually knew about the problem with delay and had been working to improve it. We were a couple days away from failing over to the n
by zeeg 11y ago
David from Sentry here.
We actually knew about the problem with delay and had been working to improve it. We were a couple days away from failing over to the new hardware (safely) and unfortunately we didn't have any early warnings in the logs. I haven't yet looked at why.
- Kassandry 11y agoHappens. Glad you're back up and running, and best of luck with your new setup. =)
- skehlet 11y agoCan you share what you had for your autovacuum_vacuum_cost_delay, and your approximate rate of transactions?
- zeeg 11y agoWe had at it 50ms on the previous setup, though I wish we I knew why that value was used. Likely it was a default with the Chef cookbook we forked off of, or we read something that convinced us at the time it was a good idea.
- JimNasby 11y agoYou need to monitor how close you are to a wraparound. https://bucardo.org/check_postgres/check_postgres.pl.html#txn_wraparound https://bucardo.org/check_postgres/check_postgres.pl.html#tx... is one way you could do that.