Those days feel really lucky to me. I’m currently visiting friends and customers in San Francisco, and really enjoying my trip here! Of course Josh Berkus took the opportunity to organise a SFPUG meeting and I had the pleasure of being the speaker over there. My talk was about the most recent version of Skytools and the opportunity to realise that we’re still missing a lot on documentation. One of the attendee did propose to help us on that front as he apparently really likes technical writing.
Some skytools related new today, it’s been a while. For those who where at my FOSDEM’s talk about Implementing High Availability you might have heard that I really like working with PGQ. A new version has been released a while ago, and the most recent verion is now 3.1.3, as announced in the Skytools 3.1.3 email. *Upgrade time!* Skytools 3.1.3 enters debian First news is that Skytools 3.1.3 has been entering debian today (I hope that by the time you reach that URL, it’s been updated to show information according to the news here, but I might be early).
Now that you’re all using the wonders of Cooperative Consumers to help you efficiently and reliably implement your business constraints and offload them from the main user transactions, you’re reaching a point where you have to clean up your development environment (because that’s what happens to development environments, right?), and you want a way to start again from a clean empty place. Here we go. It used to be much more simple than that, so if you’re still using PGQ from Skytools2, just jump to the next step.
While working a new PostgreSQL architecture for an high scale project that used to be in the top 10 of internet popular web sites (in terms of visitors), I needed to be able to off load some processing from the main path: that’s called a batch job. This needs to be transactional: don’t run the job if we did rollback; the transaction, process all events that were part of the same transaction in the same transaction, etc.