@AndresFreundTec

6.5K Followers
79 Following
427 Posts

Long time postgres developer, working at Microsoft.

Account about tech, not politics. For the latter look to @AndresFreundPol

Blueskyhttps://bsky.app/profile/anarazel.de

For our own compute we've been averaging daily:
- 1464 core hours (full cores, not SMT)
- 396 of which were windows (visible due to the licensing cost)
- 40GB of artifacts
- doesn't include macos, which I can't track as easily, due to being self hosted runners

So we will likely need something where we can continue to provide compute ourselves, to keep this affordable.

Any suggestions / experiences where to look next?

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

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

“Floating-Point Printing and Parsing Can Be Simple And Fast”

The fastest known floating-point printer and parsing algorithms - fixed-width printing, shortest-width printing, and parsing, all in 400 lines of Go.

https://research.swtch.com/fp
https://research.swtch.com/fp-proof

research!rsc: Floating-Point Printing and Parsing Can Be Simple And Fast (Floating Point Formatting, Part 3)

If you work on postgres or work intensively with postgres, you should consider submitting a talk to this year's pgconf.dev - the CFP deadline closes tomorrow! It's by far my favorite conference of the year!

https://2026.pgconf.dev/cfp

That experience has stopped me from making some terrible UX choices over the years (although I still have committed plenty UI crimes).

Got my start into making money with computers helping seniors learn computers. To this day I remember trying and failing to give a short & coherent explanation of when to use single clicks and when double clicks in Windows (must have been 98 and XP), File Explorer and Browsers. And the despair of the seniors not understanding..

Never really could come up with something that was better than "you should intuitively know".

Hoped for effect of AI use of new postgres contributors: Faster rampup, higher quality patches.

Real effect: A torrent of pointless patches, which often don't even pass tests. A torrent of AI generated pointless review comments.