Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
fuy
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
31.
▲
by
fuy
3y ago
a bit off topic, but do you know of any good resources on tuning battery life and CPU fan control for system76 laptop?
32.
▲
by
fuy
3y ago
This basis is our limited data set: we have only 1 example of human level intelligence, so it's natural to assume there's something unique, or at least significant about the way it works.
33.
▲
by
fuy
3y ago
it's probably been mentioned before, but there are customers that require IPv6 (like some US gov agencies and others), so for a lot of B2B/enterprise software companies it actually makes sense to support ipv6. And it's techni
34.
▲
by
fuy
3y ago
they can have their own databases, but still be on the same Postgres instance (aka cluster in Postgres parlance).
35.
▲
by
fuy
3y ago
> low because I didn't care of philosophy or other non CS classes For all people saying that philosophy is not important for engineering/cs grads - here's the proof it is!
36.
▲
by
fuy
3y ago
Alexander Korotkov (OrioleDb author) idea, - based on his Postgres committer experience, I believe, - is that these changes are way too big to be ever accepted upstream, hence separate engine. More info https://www.socallinuxexpo
37.
▲
by
fuy
3y ago
I think the blog author uses it the same way Codd does, that's why he's talking about two columns from the same table.
38.
▲
by
fuy
3y ago
I don't think Timothy Snyder himself would be glad to be a part of this ridiculous take.
39.
▲
by
fuy
3y ago
70% supporting the war is way way of. Active supporters are likely in 20-25% range, majority would definitely be happy with any reasonable peace deal.
40.
▲
by
fuy
3y ago
There's columnar tables in SQL Server, though. Have you tried it? Would be interesting to compare to Snowflake.
41.
▲
by
fuy
3y ago
I would love for it to have a second edition soon. Wonderful book.
42.
▲
by
fuy
3y ago
wtf, this is just a lie. Have your looked at actual casualty numbers in 2016-2021? i.e after the initial bloodbath that Russians started in 2014 and that finished in 2015. it's been around 100 killed per year (both civilians and army)
43.
▲
by
fuy
4y ago
Well, that was the whole premise of the question though. Of course there are many millions of Russians who oppose the war and who still stay in Russia. And some of them are not staying quiet.
44.
▲
by
fuy
4y ago
In my experience, Rider is much a better IDE for development, especially on large codebases. In our few million LOC codebase, VS lags/hangs a lot, navigation is slow, search (like searching for a log string in a codebase) is awfully sl
45.
▲
by
fuy
4y ago
Simple views are perfectly fine - it's mostly nesting of views with aggregate functions and other complicated stuff that is bad. And if ad-hoc is a big part of what users are doing with an app/database and you don't care abo
46.
▲
by
fuy
4y ago
> slather a battery of views over your data One needs to be careful with this approach in terms of query performance, though. Using simple views with a couple of joins and some filtering is fine, but be very wary of stacking more than 1-
47.
▲
by
fuy
4y ago
CMU's Andy Pavlo database courses and related webinars https://m.youtube.com/playlist?list=PLSE8ODhjZXjaKScG3l0nuOi... https://m.youtube.com/playlist?list=PLSE8ODhjZXjaKScG3l0nuOi...
48.
▲
by
fuy
4y ago
without ORDER BY in the outermost query the ordering is definitely not guaranteed and may be influenced by optimizations
49.
▲
by
fuy
4y ago
Definitely agree. I've been trying to go full-Vim a few times over the years, and it's not been very successful. I'm a huge fan of Vim keybindings though, and wouldn't use an editor/IDE without support for it. I wou
50.
▲
by
fuy
4y ago
> As far as SQL (the language and the standard) is concerned, SQL is unaware of threads or the thread safety; SQL is concerned with transactions and with the transactional integrity. The database provides and ensures the ACID behaviour a
51.
▲
by
fuy
4y ago
Some of the ones that I haven't yet seen mentioned: "Oxide and Friends" is a great interdisciplinary podcast with a lot of focus on hardware and low-level stuff, but always looking at a big picture. "Array Cast" is
52.
▲
by
fuy
4y ago
sounds interesting, will definitely listen to a few episodes!
53.
▲
by
fuy
4y ago
My main gripe is the idea that MERGE is somehow better than INSERT ON CONFLICT for upserts, which I don't think is ever true. I don't think I agree that it was added as a workaround - it was added rather as a proper solution, but
54.
▲
by
fuy
4y ago
there's also things like pg_repack which don't lock the tables (but will incur high IO while freeing up the space).
55.
▲
by
fuy
4y ago
Why would you want to replace upserts (I.e INSERT with ON CONFLICT) with MERGE? Without additional context I'd say it's an antipattern, for a few reasons. First is that MERGE is a much more versatile operator (not a compliment if
56.
▲
by
fuy
4y ago
> Perhaps it's just me, but I don't equate optional with nullable. But the main usage of Optional and similar types in mainstream languages is exactly that - making the potential nullness (is that a word?) of the value explicit
57.
▲
by
fuy
4y ago
What a neat switch from metric to imperial units! I wish more web pages had this.
58.
▲
by
fuy
4y ago
Having migrated large codebase/product from SQL Server to Postgres, can definitely relate. I love Postgres as a developer, but from DBA/devops perspective, Postgres requires babysitting where SQL Server just works. Things like hav
59.
▲
by
fuy
4y ago
They mention that they measure "cache coherence protocol" throughput. So yes, this happens when two or more cores need to work on the same memory and they need to synchronize/update what is in their L1 and L2 (and probably L3
60.
▲
by
fuy
4y ago
I think you've just discovered Curry-Howard isomorphism!
More ›