Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
fdr
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
21 ms
·
151.
▲
by
fdr
5y ago
> That took an extremely long time. (three days? am I reading the issue right?)
152.
▲
by
fdr
5y ago
EVs still drive on roads.
153.
▲
by
fdr
5y ago
My favorite WillSoft so far is his emoji film renderer. https://youtu.be/v32XHJxljKI?t=876
154.
▲
by
fdr
5y ago
I also like the Awair Element. Enough that I bought two.
155.
▲
by
fdr
5y ago
This was one of the more useful things Heroku ever seeded, though the maintenance in the intervening decade has certainly eclipsed the initial effort ( https://blog.heroku.com/postgresapp_the_easiest_way_to_devel... ). These
156.
▲
by
fdr
5y ago
Do VPCs or subnets aggregate a larger block that can be used to write a firewall rule? I wouldn't find it quite as useful to have per-VM blocks issued piecemeal. It's not clear from the documentation that I read.
157.
▲
by
fdr
5y ago
I often weigh the value of comments -- I used to write more, now I write fewer -- by weighing odds of utility against decay into misinformation. Comments conveying something of high utility that is fundamental to the program and unlikely to
158.
▲
by
fdr
6y ago
If you ever measure the improvement, a brief note/blog post/tweet might instructive to people. Would be curious what kind of different result you get.
159.
▲
by
fdr
6y ago
You mean physical, re: skepticism. Just different things. Bulky for "CREATE INDEX" or "VACUUM", but also faster for a lot of things (no decoding) and able to more naturally deal with incomplete transactions. A good way t
160.
▲
by
fdr
6y ago
Yeah, there's some kludgey workaround for this that is definitely 80/20 kind of material...pg_upgrade will generate a script that does progressively more accurate re-ANALYZE so you're not flying your early queries totally bli
161.
▲
by
fdr
6y ago
I don't think the post informs on Physical and Logical replication that well. Most database systems of adequate budget and maturity implement both, for various reasons.
162.
▲
by
fdr
6y ago
I think this is a reasonable list of weaknesses, with a few quibbles. I guess since I've built parts of Heroku Postgres, and Citus Cloud, and now Crunchy Bridge...maybe I'd know. On the other hand...on the whole...maintaining Post
163.
▲
by
fdr
6y ago
Hmm, I think you are looking for SP-GiST (unbalanced space partitioned GiST), unless you meant that implicitly. It can be much faster for...space partitioning.
164.
▲
Query Optimization in Postgres with pg_stat_statements
(blog.crunchydata.com)
12 points
by
fdr
6y ago
|
0 comments
165.
▲
A Bug on Aurora PostgreSQL 12 causes Autovacuum to hang forever
(migops.com)
4 points
by
fdr
6y ago
|
0 comments
166.
▲
Cleaning Up Your Postgres Database
(info.crunchydata.com)
3 points
by
fdr
6y ago
|
0 comments
167.
▲
by
fdr
6y ago
These do not make fifty thousand opex per homeless person per year or anything around that. Both before and onwards, much is capex to build out.
168.
▲
by
fdr
6y ago
> San Francisco spends $50k per homeless person. A commonly repeated falsehood. Is totally incorrect. https://www.sfchronicle.com/bayarea/heatherknight/article/Bu...
169.
▲
by
fdr
6y ago
May be worth reading this article about Harvard's endowment consolidating water rights in California as well. https://www.wsj.com/articles/harvard-quietly-amasses-califor...
170.
▲
Understanding Recursive Queries in PostgreSQL
(cybertec-postgresql.com)
168 points
by
fdr
6y ago
|
43 comments
171.
▲
Control Runaway Postgres Queries with Statement Timeout
(info.crunchydata.com)
2 points
by
fdr
6y ago
|
0 comments
172.
▲
by
fdr
7y ago
Yelp has also done this. It's very (or rather, isn't very) noticeable on mobile, where it takes some attention to see if you are in algorithmic or sponsored results. Looks like Overture/Goto.com was a bit too early, and a bit
173.
▲
by
fdr
7y ago
Do not agree. Commit messages can be more expansive than comments, because comments bitrot more readily: they are not rooted in a time and change to the code. I use commits for the largest bulk of explanation, particularly "why,"
174.
▲
by
fdr
7y ago
The "straightforward" way to deal with this is a multi-year project. So, the reason is likely expense. The guts of the matter is that Postgres, and its extensions, relies on a number of global variables. These global variables are
175.
▲
by
fdr
7y ago
That's probably true. The only tell for that, really, was the complexity around migrations/schema changes, which seems a lot more painful on MySQL.
176.
▲
by
fdr
7y ago
There seems to be a certain mysql tinge to this value calculation. I use foreign keys and like it (I use Postgres). I do not encounter the problems the author does. I omit them when they are a problem for some reason. This is rare in routin
177.
▲
by
fdr
8y ago
I sort of commissioned the project at Citus, under the auspices of figuring out how much memory copies were costing WAL-E. The answer was: a lot. Our main goal was to touch as many risk points as possible in the design of WAL-E replacement,
178.
▲
by
fdr
8y ago
I like the gist of this approach. A few years ago, I read about some books of the legendary (non-software) engineering projects in the past. Engineers were very cognizant of risk and costs, far more than I see in software practice. With som
179.
▲
\watch-ing Star Wars in Postgres
(citusdata.com)
4 points
by
fdr
8y ago
|
0 comments
180.
▲
by
fdr
8y ago
Don't get discouraged, if you were feeling that way. It was important you substantiated the envelope of what kind of improvements are theoretically possible. And although the wealthier residents, who really ought to have the property t
More ›