702 karma · joined September 17, 2014
[0] http://www.menteach.org/resources/data_about_men_teachers
It's a dangerous path, and sadly somehow you're seen as a racist if you speak out against it - I'm willing to accept down votes to speak the truth, as we all should.
Singling out specific ethnic groups to hire is wrong, it's that simple.
If vacuums are hanging/causing locks and these truly are just test tables, it might be beneficial to use temporary tables instead as the autovacuum daemon ignores them. Additionally, unlogged tables that reside on a memory disk can be insanely fast - might cut some additional time down depending on your data.
I realize this wasn't their solution, but it's worth noting that generally speaking, disabling auto-vacuum isn't recommended. Even if you do, it will still force vacuum jobs to prevent transaction ID wraparound.
* https://www.postgresql.org/docs/9.5/static/routine-vacuuming...
Lots of fats, proteins, and veggies, staying away from carbs and sugar, and I feel better than any other time in my entire life (at 34). I'm no longer eating simply to eat, and at this point I'm not craving the crap I used to. The sickness that now ensues after ingesting processed sugars or carbs, does make it easy to skip. While this story is anecdotal, it seemed worth a try because I kept stumbling on research supporting it.
I do however take great offense to being referred to as a xenophobe simply because of where I live, that's asinine.
I'd much rather see the market address these concerns without being coerced into doing so. If consumers want a big "emergency" button on their phone, by all means offer a product with one, but forcing said "feature" on every single person who purchases a phone should be frowned upon.
"The drawbacks are high latency in both reads and writes and low throughput. Pg_paxos cannot be used for high performance transactional systems. But it can serve very well for low-bandwith, reliable replication use cases."