Elektrine lite

← Feed

AndresFreundTec

AndresFreundTec@mastodon.social

<p>Long time postgres developer, working at Microsoft.</p><p>Account about tech, not politics. For the latter look to <span class="h-card" translate="no"><a href="https://mastodon.social/@AndresFreundPol" class="u-url mention">@<span>AndresFreundPol</span></a></span></p>

Posts

  • Post #3641238

    A few days ago, at @pgconfdev, 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

  • Post #2096821

    That&amp;#39;d work, but the better fix is to simply not have the lock in the first place :). Which we did a few months ago...

  • Post #2096820

    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.

  • Post #2096819

    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&amp;#39;s not clear what they were after. Not a straight attempt at relaying SMS &amp;quot;2FA&amp;quot; or such. Played along until they wanted me to repeat a case number back to them, which see...

  • Post #2092815

    I accidentally found a security issue while benchmarking postgres changes. If you run debian testing, unstable or some other more &amp;quot;bleeding edge&amp;quot; distribution, I strongly recommend upgrading ASAP. https://www.openwall.com/lists/oss-security/2024/03/29/4

  • Post #1075286

    Postgres until now has been using cirrus-ci for CI. Unfortunately they&amp;#39;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 lo...