HN user

karsinkk

227 karma

Software Engineer@Oracle, Working on the RDBMS Engine

Posts73
Comments32
View on HN
cdouglas.github.io 4mo ago

Simulating Catalog and Table Conflicts in Iceberg

karsinkk
1pts0
smalldatum.blogspot.com 9mo ago

Is it time for TPC-BLOB?

karsinkk
2pts0
oracle.github.io 9mo ago

Open Agent Specification (Agent Spec): A Unified Representation for AI Agents

karsinkk
1pts0
database-doctor.com 1y ago

Iceberg, the Right Idea – The Wrong Spec – Part 2 of 2: The Spec

karsinkk
1pts0
en.wikipedia.org 1y ago

Dunbar's Number

karsinkk
2pts0
madcompiler.blogspot.com 1y ago

Portable Inline Assembly

karsinkk
2pts0
lcamtuf.coredump.cx 2y ago

Delivering Signals for Fun and Profit (2001)

karsinkk
9pts0
en.wikipedia.org 2y ago

1950s Quiz Show Scandals

karsinkk
3pts0
brooker.co.za 2y ago

It's About Time

karsinkk
1pts0
engineercodex.substack.com 2y ago

One line of code caused a $60M loss

karsinkk
5pts0
www.wsj.com 2y ago

One of the Greatest Comebacks in Sports History (2013)

karsinkk
1pts0
finshots.in 2y ago

Byju's refuses to repay its $1.2B loan

karsinkk
3pts0
en.wikipedia.org 2y ago

Jimmy Carter rabbit incident

karsinkk
12pts7
thephd.dev 3y ago

To Save C, We Must Save ABI (2022)

karsinkk
64pts15
narratively.com 3y ago

The (Literally) Story of the Original Fake News Network

karsinkk
2pts0
www.vanityfair.com 3y ago

The Murdoch Succession

karsinkk
12pts6
restofworld.org 3y ago

The rise and fall of Argentina’s celebrity crypto pastor

karsinkk
4pts0
www.vanityfair.com 3y ago

The Murdoch Succession

karsinkk
3pts0
docs.oracle.com 3y ago

Lock-Free Reservation in Oracle Database 23c

karsinkk
2pts0
dealbreaker.com 3y ago

A Whale of a Fail

karsinkk
2pts0
blogs.oracle.com 3y ago

JSON Relational Duality: Convergence of Document, Object, and Relational Models

karsinkk
5pts1
thegreatestgrid.mcny.org 3y ago

The Greatest Grid – Master Plan of Manhattan

karsinkk
4pts0
www.worksinprogress.co 3y ago

The decline and fall of the British economy

karsinkk
4pts0
maroonmacro.substack.com 4y ago

Commercial Banks and the Real Economy

karsinkk
2pts0
stacker.com 4y ago

Every recession from U.S. history and how the country responded (2020)

karsinkk
11pts0
aws.amazon.com 4y ago

Hidden dangers of duplicate key violations in PostgreSQL and how to avoid them

karsinkk
2pts0
www.joelonsoftware.com 4y ago

The Absolute Minimum Every Developer Must Know About Unicode and Character Sets

karsinkk
3pts0
www.open-std.org 4y ago

Fibers under the magnifying glass [pdf]

karsinkk
28pts7
engineering.fb.com 4y ago

Delos: Simple, flexible storage for the Facebook control plane

karsinkk
4pts0
www.economist.com 4y ago

Argentina and Japan continue to confound macroeconomists

karsinkk
1pts0

" Combined with this only happening in a corner case (stale sessions) and the difficulty of reproducing the issue, it took us over a week to discover and confirm the root cause"

I don't know about others, but sessions that are idle > 1h are definitely not a corner case for me. I use Claude code for personal work and most of the time, I'm making it do a task which could say take ~10 to 15mins. Note that I spend a lot of time back and forth with the model planning this task first before I ask it to execute it. Once the execution starts, I usually step away for a coffee break (or) switch to Codex to work on some other project - follow similar planning and execution with it. There are very high chances that it takes me > 1h to come back to Claude.

I was going over some of the code in the core folder for concurrency, threading and compression, what surprised me is that there’s absolutely no comments whatsoever. Agree that unless there’s excellent documentation, open source maintenance might be challenging.

Having said that, this definitely does look to be an impressive feat of engineering!

While transforming the plan into vectors is interesting, I wish they'd gone into more detail about how the ML model prunes and filters the best plan. It is also not clear what attributes of a plan the corresponding vector encodes. I do not know much about Databloom, but it looks like this "Learning-Based Query Optimizer" is built for specific use-cases in a Data engineering/analytics setting(like K-means as cited in the article). It might not be a replacement for optimizers in traditional Databases.

I've noticed the same behavior with the recommendation engine from Reddit and Instagram as well. While they don't totally block providing feedback on recommended posts that I'm actually not interested in, the UI flow to submit the feedback is difficult/confusing enough that I've just stopped doing it altogether. Could this be because retraining whatever model that they've built is difficult/expensive with new feedback?

You're right, A hash function doesn't map to multiple values. Bloom filters and other probabilistic set membership DS's like Cuckoo filters instead use multiple hash functions to map one input to multiple output values. [1] The number of hash functions to use depends on the expected false positive probability rate, number of bits in the filter and the number of elements which will be inserted

[1] https://en.wikipedia.org/wiki/Bloom_filter#Algorithm_descrip...

GitHub Copilot 5 years ago

I still haven't gotten my hands on the Beta yet, so I'm not sure how it's going to be deployed; But does anyone know if Copilot is going to be accessible through some online IDE (or) is it going to be through an extension for VS Code/other editors? If it's the latter, I hope the extension doesn't eat up all my CPU!

Agreed. This feel more like an involuntary social experiment and it just uses up the Kernel maintainers bandwidth. Reviewing code is difficult, even more so when the committer is set out to introduce bad code in the first place.

Here's a clarification from the Researchers over at UMN[1].

They claim that none of the Bogus patches were merged to the Stable code line :

Once any maintainer of the community responds to the email,indicating “looks good”,we immediately point out the introduced bug and request them to not go ahead to apply the patch. At the same time, we point out the correct fixing of the bug and provide our proper patch. In all the three cases, maintainers explicitly acknowledged and confirmed to not move forward with the incorrect patches. This way, we ensure that the incorrect patches will not be adopted or committed into the Git tree of Linux.

I haven't been able to find out what the 3 patches which the reference are, but the discussions on Greg's UMN Revert patch [2] does indicate that some of the fixes have indeed been merged to Stable and are actually Bogus.

[1] https://www-users.cs.umn.edu/~kjlu/papers/clarifications-hc....

[2] https://lore.kernel.org/lkml/20210421130105.1226686-1-gregkh...

Autonomous JSON Database costs 30% less than comparable MongoDB Atlas configuration.

Autonomous JSON database gives you 2x throughput consistently across different workload types and collection sizes.

This is great!

The result is a no-compromise document database providing low latency CRUD operations and full ACID consistency.

The recent Jepsen report[1] highlights some of the major transaction consistency issues with MongoDB and why it might not be suitable for all workloads.

[1] http://jepsen.io/analyses/mongodb-4.2.6