Transaction ID Wraparound in Postgres

Re:Transaction ID Wraparound in Postgres by zeeg on Thursday July 23, 2015 @02:32PM (#9937596)

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.

[ Parent | on HN ]

Re:Transaction ID Wraparound in Postgres by JimNasby on Thursday July 23, 2015 @06:33PM (#9938915)

You need to monitor how close you are to a wraparound. https://bucardo.org/check_postgres/check_postgres.pl.html#tx... is one way you could do that.

[ Parent | on HN ]

Re:Transaction ID Wraparound in Postgres by skehlet on Thursday July 23, 2015 @03:54PM (#9938075)

Can you share what you had for your autovacuum_vacuum_cost_delay, and your approximate rate of transactions?

[ Parent | on HN ]

Re:Transaction ID Wraparound in Postgres by zeeg on Friday July 24, 2015 @12:56AM (#9940175)

We 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.

[ Parent | on HN ]

Re:Transaction ID Wraparound in Postgres by Kassandry on Thursday July 23, 2015 @03:27PM (#9937916)

Happens. Glad you're back up and running, and best of luck with your new setup. =)

[ Parent | on HN ]