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

Pinned
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
Jeremy Schneider
@jer_s
8h
love this!
Bertrand Drouvot
@BertrandDrouvot
9h
Welcome to pg_walviz: #PostgreSQL WAL segment visualizer: bdrouvot.github.io/2026/08/13/wel…
Jeremy Schneider
@jer_s
11h
if you think reading source code is over, consider that postgres hackers still scrutinize hardware level cpu instructions despite the existence of compilers. the top engineers will still be ones who understand code. examples: postgresql.org/message-id/CAO… and postgresql.org/message-id/202…
postgresql.org
Optimizing COPY with SIMD
Inspired by David Rowley's work [1] on optimizing JSON escape processing with SIMD, I noticed that the COPY code could …
Jeremy Schneider
@jer_s
Aug 12
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…
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.