anarazel

36 ms·

151.
by anarazel 3y ago
And the dispatch overhead will be a few orders of magnitude higher.
152.
by anarazel 3y ago
You can see this stuff often even in test workloads. But even if you disregard that kind of issue, you still have stuff like needing to integrate networked database connections into e.g. event loops, which you don't really need to do f
153.
by anarazel 3y ago
I'd say that in-memory/not-in-memory isn't the big difference - it's whether your database is in-process or not. Even with just a database running on the same node, but in a different process, connected to via unix socke
154.
by anarazel 3y ago
Hm? I live in SF and it's considerably below that on average? https://www.bls.gov/regions/west/news-release/averageenergyp... says the area averages ~0.35$
155.
by anarazel 3y ago
If some annotations or such would make that easier, it might be possible to do that upstream. Postgres currently has hand-generated code for tab-completion in psql and that's uh, not great (it has gotten large enough that msvc has trou
156.
by anarazel 3y ago
Have you investigated generating your parser from postgres' gram.y instead of basically basing it on the bison output?
157.
by anarazel 3y ago
When will you contribute?
158.
by anarazel 3y ago
https://sqlite.org/draft/jsonb.html references postgres: > The "JSONB" name is inspired by PostgreSQL, but the on-disk format for SQLite's JSONB is not the same as PostgreSQL's. The two formats
159.
by anarazel 3y ago
My main issue with them is not their content proper, but that their SEO ranks them above much more topical results. That's clearly also Google's fault, but it's also clearly w3school's strategy.
160.
by anarazel 3y ago
I've seen lost completed FUA writes on enterprise drives quite a few times.
161.
by anarazel 3y ago
Getting a driver's license in Germany costs well over an order of magnitude more than in the US and takes quite a few weeks. And speed limits are much more enforced in the Germany compared to the US.
162.
by anarazel 3y ago
> My gut feeling tells me that the chances of having an upstream library that contains the parser/parse analysis/planner are slim. Yea. The parser alone would be doable and not even that hard. But once you get to parse analysis
163.
by anarazel 3y ago
> The applied heuristic in this case apparently being "join tables by order of lower row count". Not really - it's all cost based analysis. There are a few main culprits that might be at work: 1) Selectivity estimates can
164.
by anarazel 3y ago
I don't think <stacktrace> is async signal safe, and thus shouldn't be used for in-process crash reporting.
165.
by anarazel 3y ago
For GPUs it only really works because the code is translated to the relevant instruction steam close to the time of executing, where you can afford to optimize in a highly uarch specific way. Whereas VLIW at the time of itanium never was in
166.
by anarazel 3y ago
My experience with folks proudly proclaiming "100% coverage" is that it's typically "just" line coverage, even if you're obviously right.
167.
by anarazel 3y ago
When writing in loosely typed languages, some folks aim for 100% line coverage, to make it more feasible to refactor down the line. Which then of course ends up being a lot of tests for fairly basic stuff that the type system could help you
168.
by anarazel 3y ago
Yea. I've long since given up on that ever being correct. Too many people with too many mail clients. Thus for many mime types I just force that to be redone: mime_lookup application/octet-stream application/x-gzip applic
169.
by anarazel 3y ago
> > I find lkml style patch handling bad as well, particularly with every patchset revision getting its own thread. Very easy to loose track. > This is a good point, but if it works for the largest open-source software project in t
170.
by anarazel 3y ago
> - It is hard to get patches looked at, even small ones. With better name recognition in the community, comes more patch reviews it seems, which is most likely the case in most projects, but still, it is a circular issue. I agree that t
171.
by anarazel 3y ago
> How much bigger (in lines of code) is Postgres now versus the one from 15 years ago? I was curious as well and wrote a, very crude, script to measure it: for t in $(git tag -l|grep -E 'REL.*_0$|REL[67]_[0-4]$'|grep -v RE
172.
by anarazel 3y ago
(postgres hacker) Yes, I think that will be the case. Obviously not a scientifically measured, by I think we're already seeing that average C skills for new contributors are lower than what they used to be - of course that might just b
173.
by anarazel 3y ago
Isn't the loss for dimensional lumber more due to drying than finishing?
174.
by anarazel 3y ago
From very dim memory: I think there's some flag you can set that marks your test network as not suitable for that kind of thing. But even if not, IIRC you can set routing information for stuff like 911 on a subscriber basis in your tes
175.
by anarazel 3y ago
Can't you stand up your own test network for that? Other phones won't connect to that, so you don't need to fully rf isolate, as long as you have some trust in the test network not doing crazy things. It's well over a de
176.
by anarazel 3y ago
> postgres requests an id from the sequence for each row of the incoming data ahead of time since it doesn't know which rows are updates and which are inserts (although presumably this could be changed?). Not in any sort of general
177.
by anarazel 3y ago
> Postgres is VERY committed to making sure a replication slot’s consumer doesn’t miss any data. This means that if a consumer stops consuming data from the slot, Postgres will helpfully store all that missed data… right up until the dis
178.
by anarazel 3y ago
> Did the switch? Does postgres use a VM now? Yes (to me my comment seemed to make that clear, but...). Didn't really remember how long ago that was, so I dug up the commit. Main commit went in ~6.5 years ago. There were lots of re
179.
by anarazel 3y ago
It really depends on the query. If there's a bunch of math in the select list, it's easy for that to be the biggest bottleneck, even if there are joins etc. Also you'll sometimes have to evaluate expressions to check join con
180.
by anarazel 3y ago
Another related aspect is that the VM approach can allow JITing only some of the opcodes, which makes it more feasible and maintainable.

More ›