kmdupree

17 ms·

181.
Optimizing Postgres Queries at Scale(heap.io)
2 points by kmdupree 5y ago|0 comments
182.
Hiring for Expertise You Don't Have(heap.io)
1 points by kmdupree 5y ago|0 comments
183.
We saved millions in SSD costs by upgrading our filesystem(heap.io)
654 points by kmdupree 5y ago|311 comments
184.
We Saved Millions in SSD Costs by Upgrading Our Filesystem(heap.io)
3 points by kmdupree 5y ago|1 comments
185.
by kmdupree 5y ago
RETURNING * is a clever way to do this. What is this * from affected_rows syntax you're using here? Any chance you have a link to the docs that describes this?
186.
by kmdupree 5y ago
clever! hadn't thought of combining this with hstore.
187.
by kmdupree 5y ago
Thanks for sharing these links!
188.
by kmdupree 5y ago
Ah. Sorry to disappoint. The technique was just new to me, so I thought it was worth sharing. :)
189.
by kmdupree 5y ago
Author here. :) >I have used it in at least one application before. Good to know that other folks are using this technique! >One of my favorite things about it is that you can use it even when you don't own the application writin
190.
Postgres audit tables saved us from taking down production(heap.io)
174 points by kmdupree 5y ago|57 comments
191.
by kmdupree 5y ago
Great question! I should have been clearer. Each event type gets a new partial index where the WHERE clause of the partial index corresponds to the properties of the new event type. Hope that clarifies! Lmk if not. :)
192.
Rolling out 1M Postgres indexes(heap.io)
13 points by kmdupree 5y ago|2 comments
193.
by kmdupree 5y ago
Great question! For new events we have 8 workers that process multiple customers at a time so the time to querability is typically pretty fast!
194.
The Million Indexes Incident(heap.io)
3 points by kmdupree 5y ago|2 comments
195.
The Million Indexes Incident(heap.io)
2 points by kmdupree 5y ago|0 comments
196.
We Turned Our Front-End Code into a Component Library (and You Can, Too)(heap.io)
2 points by kmdupree 5y ago|0 comments
197.
by kmdupree 5y ago
Thanks for reading! I hear you on visibility maps being intimidating. In practice, I haven't seen any cases where visibility map issues have prevented an index-only scan. But we did initially think that the visibility map was to blame
198.
by kmdupree 5y ago
You're exactly right that our schema could be better and that it's non-trivial to execute on a schema change, especially because we actually run a distributed Postgres cluster via Citus AND we use a special sharding method that we
199.
Working around a case where the Postgres planner is “not very smart”(heap.io)
65 points by kmdupree 5y ago|59 comments
200.
How and When to Control for Confounders During Product Usage Analyses(heap.io)
1 points by kmdupree 5y ago|0 comments
201.
How and When to Control for Confounders During Product Usage Analyses(heap.io)
2 points by kmdupree 5y ago|0 comments
202.
Building Better Code Review at Heap(heap.io)
3 points by kmdupree 6y ago|0 comments
203.
by kmdupree 6y ago
Glad we agree! (I'm the author) Less bike shedding => more substantial review comments => better code
204.
Building Better Code Review at Heap(heap.io)
2 points by kmdupree 6y ago|2 comments
205.
When should we create abstractions instead of duplication?(philosophicalhacker.com)
1 points by kmdupree 6y ago|0 comments
206.
Programming and Forecasting(philosophicalhacker.com)
2 points by kmdupree 6y ago|0 comments
207.
Why Mobile Dev IDEs Are Bad(philosophicalhacker.com)
1 points by kmdupree 6y ago|0 comments
208.
Show HN: Authorx (extensible, markdown-like language for creating rich content)(philosophicalhacker.com)
1 points by kmdupree 6y ago|0 comments
209.
A Tidy Analysis of Astronauts and Their Missions(philosophicalhacker.com)
1 points by kmdupree 6y ago|0 comments
210.
Show HN: VSCode plugin that shows how frequently source files have changed(marketplace.visualstudio.com)
1 points by kmdupree 6y ago|0 comments

More ›