anarazel

61 ms·

511.
by anarazel 6y ago
I don't understand how an increase, including the implied variability, of CPU internal parallelism and VLIW benefits go together?
512.
by anarazel 6y ago
IMO VLIW is an absurdly bad choice for a general purpose processor. It requires baking in a huge amount of low level micro-architectural details into the compiler / generated code. Which obviously leads to problems with choosing what h
513.
Contagion Externality of a Superspreading Event: Sturgis Bike Rally and COVID19 [pdf](ftp.iza.org)
6 points by anarazel 6y ago|0 comments
514.
by anarazel 6y ago
That seems more like a leadership than an employee issue.
515.
by anarazel 6y ago
The release notes are directly referencing that they copied us / PG: "Support for UPDATE FROM following the PostgreSQL syntax. The sqlite folks have done that a few times, and I think that's good. No need to unnecessarily pr
516.
by anarazel 6y ago
And yet they're quite profitable...
517.
by anarazel 6y ago
They don't debunk anything. The last study you quote says "this highlights the importance of safety practices including face masks and ocular contact precautions in preventing the spread of COVID-19 disease.". Another is a me
518.
by anarazel 6y ago
Thanks for the update. > edit: PS, thanks for the idea of putting what I assume is the backend pid in psql's prompt. I need to go figure out how to do that right now! Here's my ~/.psqlrc: andres@awork3:~/src&#x2
519.
by anarazel 6y ago
> Enforcement is the state forcing its will on you eliminating the individual’s ability to evaluate risk. Except that the primary benefit of masks wrt covid is to significantly reduce the likelihood of the wearer to spread covid (by r
520.
by anarazel 6y ago
The US wide totals are muddling the picture substantially. Deaths have continued to shrink substantially in previously severely affected states like NY or NJ. The other big issue of course is lag. If you look at daily positive tests, curren
521.
by anarazel 6y ago
> Even as the number of cases goes up, deaths (the more important number) keeps coming down. > We keep hearing about how this trend will reverse soon, ("two weeks from now"), but that hasn't happened yet. Your graph sho
522.
by anarazel 6y ago
The largest part of the time executing the above query isn't inside the function, so this isn't that a material comparison. The reason for that is that SRFs in FROM to be materialized into a tuplestore, which isn't free:
523.
by anarazel 6y ago
x86 instructions I'd like to see are atomic instructions with lower global memory ordering guarantees. TSO is nice, but there's enough performance sensitive concurrent code where opting out would be useful.
524.
by anarazel 6y ago
FWIW, you already can use postgres' logical decoding / change data capture to make queuing more efficient. Depending on what you need. If it's the type of queue that various consumers need to see in their entirety, then you c
525.
by anarazel 6y ago
The aim of 230 was explicitly to allow doing so. And how would you even imagine this working? Have a bunch of conlaw students judge posts against complex tests?
526.
by anarazel 6y ago
[2] seems to be dead. > One place cockroach radically differs from postgres is that it stores historical versions of rows and it stores them sequentially. This means that if you have an update-heavy workload and you do not lower your GC
527.
by anarazel 6y ago
Not centrally anywhere, as far as I am aware of. There's a few user visible one that need explicit options to be enabled, and there's documentation for those, of course. There's other where there's plenty source code lev
528.
by anarazel 6y ago
> (1) Because SQLite is just a function call whereas PostgreSQL is a round-trip message to a separate server process, MRigger was able to run many more test cases per second on SQLite. Yea, that made it harder in the past for other test
529.
by anarazel 6y ago
The classical solution to that is to use 2PC. But often it's not worth it...
530.
by anarazel 6y ago
I don't think that's true. There's e.g a recent study from the USS Roosevelt, and it showed to be the most effective measure. Followed by social distancing. https://www.cdc.gov/mmwr/volumes/69/w
531.
by anarazel 6y ago
Correct. Edited comment to clarify. I think there's some possibly quibbling around the edges around what exact would be included, or not. E.g. a rule that bonus / commissions don't have to be included, as long as that doesn&#
532.
by anarazel 6y ago
I think cases like this can largely be dealt with by allowing non-competes, but only as long compensation continues. Without that the power imbalances are just too extreme. EDIT: rephrased to make clear I wasn't just referring to base
533.
by anarazel 6y ago
Not working in sqlite, but postgres. We've found numerous bugs in gcc, clang and postgres by building / testing with unreleased compilers. And found usability issues with new compiler warnings. That doesn't mean we use such c
534.
by anarazel 6y ago
Due to the way that the LLVM dependency in postgres works, it could be packaged separately from the base postgres server package. The LLVM interfacing code is runtime loaded, and there's no error if "llvmjit.so" is not on the
535.
by anarazel 6y ago
The PGDG doesn't really exist in the form you imagine. There certainly isn't corporate members or such. It's just a descriptor for all the developers together - it's not even a well defined legal entity.
536.
by anarazel 6y ago
BRIN indexes are kind of bitmap like...
537.
by anarazel 6y ago
> Postgres admittedly cheated a bit at first with the basic JSON support, validation of JSON but then storing it in a text field didn't quite make it a full document database. Did anybody claim it was back then? > Being a compres
538.
by anarazel 7y ago
They have plenty of thermal issues too, though.
539.
by anarazel 7y ago
It obviously makes sense that creating a new PG instance will be slower than creating a sqlite database. There also is some inherent speed difference for simple queries just by virtue of sqlite not needing to context switch to a separate pr
540.
by anarazel 7y ago
> However, if statistics change, so does the query plan. So if you run a query then run the same query again with explain analyze, you don't have a guarantee of getting the same information back. And since explain analyze doesn&#x27

More ›