Yesterday, I posted a riddle:
What happens when you add and remove a column from a table in Postgres 2000 times?
Answer:
After 1598 times, you get "ERROR: tables can have at most 1600 columns"
But... the table only has 2 columns when I get the error!
So... why?
Because Postgres doesn't actually delete columns. Not from the catalog and not from data files. Deleted columns are only "soft deleted". But they still exist.
If the column ever had data, the data will still exist in the data files. It is never removed. The column is marked as "deleted" in the catalog and the query parser, planner and executor take this into consideration when planning and reading data.
Deleted columns are not cleaned up even during full vacuum.
If you run into the 1600 column limit due to deleted columns, you have to create a new table, copy the data over and drop the old one.
So... now you know how columns are (not) deleted in postgres.
Anthropic has released a major paper uncovering more about how AI models actually work.
They can trace key aspects of how it thinks, revealing step-by-step circuit mechanisms that drive its reasoning!
Here's everything you need to know:
"an interface should provide a clear separation between consumers of a system and its implementers ... this theory breaks ... as the use of a system grows and its users start to rely upon implementation details intentionally exposed through the interface" https://t.co/lOpGfeKxcD
Until you need to break out the big guns like shared examples, avoid DSL constructs like subject, let, its, and before. Stick to your old friends: variables, methods, and classes.
https://t.co/I7Xsh6EZzz
While using #Maps navigation, phone screen is off and you want to check the route: #iOS automatically unlocks, turn on screen and show the navigator just by looking at screen. #Android remains locked. +1 #iOS#iOSvsAndroid#AndroidVSiOS
In this chain of tweets I will describe my experience transition from #Android on Samsung Galaxy A50 to #iOS on iPhone SE 2020 . #iOSvsAndroid#AndroidVSiOS