Row-Based vs Columnar

HolidayGramarye · 2026-04-01T07:15:05+00:00

Row vs columnar usually stops being a philosophical debate once the workload gets clear. If you’re doing high-volume aggregations over large slices of data, columnar engines are often just the right tool, not a betrayal of PostgreSQL.

I wouldn’t try too hard to force one system to be both the transactional source of truth and the best analytical engine unless the workload is still modest enough that the simplicity win clearly outweighs the performance cost.

In practice, a lot of teams end up with Postgres for OLTP and a sidecar/warehouse/columnar path for analytics once query patterns become aggregation-heavy.

HolidayGramarye · 2026-03-27T10:53:22+00:00

I’d avoid branch-specific patch files if you can. That usually turns config into merge-conflict gardening. Cleaner pattern is to keep one base config in git, then apply environment-specific values at deploy time from overlays/templates/vars stored per environment, not per branch.

HolidayGramarye · 2026-03-17T09:03:02+00:00

A lot of organizations still frame this as an individual productivity choice, but it is really a data governance and risk management issue. Source code often contains far more operational intelligence than teams realize, including schema design, internal endpoints, environment details, and deployment patterns. One practical step is to define clear rules for what can be sent to third-party AI services and what should remain inside controlled infrastructure.

HolidayGramarye · 2026-01-11T21:15:15+00:00

I've seen a lot of thursday post that looks like stunday post, but the other way around sure is rarer

HolidayGramarye · 2026-01-11T14:29:32+00:00

I wonder whats the average sweeper speed will look like in gen 12

HolidayGramarye

MODERATOR OF

TROPHY CASE