mastodon
4.7.0-beta.1
Long time postgres developer, working at Microsoft.
Account about tech, not politics. For the latter look to @AndresFreundPol@mastodon.social
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
A few days ago, at @pgconfdev@mastodon.social, I gave a talk about some pitfalls when profiling (and benchmarking) postgres. Turbo boost, iTLB, cpuidle, ...
Slides are here:
https://anarazel.de/talks/2026-05-21-pgconf-profiling-postgres-perils/profiling-postgres-perils.pdf
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Scam attempt just now.
Supposedly somebody from google checking in about a change to my account recovery details. Contact via both phone and email, with both a robot and a brit sounding guy.
Knew a bunch of personal details (just stuff one could easily get via leaks etc).
Interesting bit is that it's not clear what they were after. Not a straight attempt at relaying SMS "2FA" or such. Played along until they wanted me to repeat a case number back to them, which seemed too risky.
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
For our own compute we've been averaging daily:
So we will likely need something where we can continue to provide compute ourselves, to keep this affordable.
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Postgres until now has been using cirrus-ci for CI. Unfortunately they're shutting down June 1st.
They had been a good fit for us because:
- some free credits so everyone could run some CI on their own
- supported providing own compute for more demanding cases (via GCP and self hosted mac HW)
- jobs ran in one-off VMs
- support for custom images allowed us to pre-install everything, keeping test times manageable
- VMs not containers was good for perf
- CI job definitions could be run locally
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Somehow the number of cases in which one needs to slap __attribute__((always_inline)) on static inline functions to prevent gcc from creating a non-inline [partial] versions in a TU seems to be steadily increasing.
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
That'd work, but the better fix is to simply not have the lock in the first place :). Which we did a few months ago...
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
Long time postgres developer, working at Microsoft. Account about tech, not politics. For the latter look to @AndresFreundPol
I accidentally found a security issue while benchmarking postgres changes.
If you run debian testing, unstable or some other more "bleeding edge" distribution, I strongly recommend upgrading ASAP.