Log inSign up
Jeremy Schneider profile banner
user avatar

Jeremy Schneider

@jer_s
Building and running reliable data platforms that scale and perform. An organizer of Seattle Postgres User Group. My opinions are my own.
Seattle, WA
about.me/jeremy_schneid…
Joined May 2011
414
Following
2,388
Followers
RepliesMedia
  • Pinned
    user avatar
    Jeremy Schneider
    @jer_s
    Jun 8, 2022
    Latest PostgreSQL Happiness Hints: collection of things that I think every production PostgreSQL stack should have. Most things here are widely accepted, but a few are biased toward my opinions (eg scaling & dynamic conn pools). Mostly not original ideas; many people helped
    Image
  • user avatar
    Jeremy Schneider
    @jer_s
    11h
    major collation update on my blog: Postgres Checkpoint Followup and Collation Visualization and Codex Luna ... three for the price of one 😀 the collation visualization is the biggest news. the Codex part is super interesting, couldn't resist including it ardentperf.com/2026/08/12/pos…
    Image
  • user avatar
    Jeremy Schneider
    @jer_s
    Feb 19
    We need to re-think OSS contribution attribution in light of AI. More than ever, it's important for committers to give credit on where the ideas are coming from. A committer can copy/paste someone else's ideas into their own prompts, and they need to give appropriate credit.
  • user avatar
    Jeremy Schneider
    @jer_s
    Jan 20
    Poisoned conn pools in Go can escalate from row-level brownouts to complete db outages. This test suite demonstrates the failure cascade and shows how PgBouncer's peering feature (v1.19+) prevents the escalation; although fixing leaks at the app level remains the true solution.