__s

Say you select nullable column into vec, Vec<Option<T>>. vec.get returns Option<Option<T>>, which distinguishes null from out of bounds

I'd like nested Nullable in ClickHouse to use CoalescingMergeTree to support postgres unchanged TOAST values easily without getting mixed up on nulls

That describes how hands off MS was with Postgres committers ime a few years ago. Useful to house them to for helpful office hours too. We'll see how that holds up post HorizonDB

I feel like a cat stuck up in a tree

LLMs are great for being nerdsniped. I started work on walshadow (reading pg wal into clickhouse) to demonstrate the project's infeasibility, but pieces started coming together into something reasonable & order of magnitude faster

The project would've been impossible for me without LLMs. & even with them there's an argument that this project is pushing complexity limits too far. But at least with ETL there's a clear feedback loop to build on

model produces lower quality code when told to break fast and move things

> giant African land snails

Brings back memories of Africanized bees

Is your manager doing code review?

With pg_clickhouse this doubled throughput while reducing memory usage. The original motivation was to supplant clickhouse-cpp to remove C++ from codebase (c++ runtime doesn't play nice with postgres runtime)

Nice not needing text parsing for postgres/clickhouse value conversions

& you can use this format over http

Sure, which is why in first comment they say

> I'd like to open another topic about the usage of LLM for review, auditing and security purposes, but I think this is a very separate thread, and we'll open discussions at the user conference before any formal discussions.

I worked at MS Vancouver office in 2019, majority was people with visa issues to US. Even I was Canadian from Ontario who ended up there because I couldn't get visa to move to SF

Brown nosing would be if Satya was awarding Trump the award

tbf GM explaining their 2700 elo moves are only understandable when vague, as elo goes up explanation becomes closer to "in this specific position there's these dpecific lines", why should 3500 elo moves have simple reasoning?

Maybe if we start with giving simple AI generated analysis of those clumsy humans with their measly 2700 elo moves

I literally had opening slide about Worse is Better when adding mysql support to peerdb. Lots of things in mysql have v1 as stupidest thing that works, then v2 fixes issues

There's a bunch of internal types like decimal vs newdecimal, binlog started out statement based until they realized uuid generation is random so added data replication on top. CDC offset started as filepos before GTID was made so offset could survive failover

There were aspects of the design I appreciated (logical slots in postgres have a bunch of drawbacks avoided by just appending to 2nd serial log which has an expiry date instead of tracking clients' offsets), but developing against protocol you learn to not try build a consistent mental model