{"id":1321,"date":"2009-11-20T22:59:00","date_gmt":"2009-11-21T06:59:00","guid":{"rendered":"http:\/\/www.chesnok.com\/daily\/2009\/11\/20\/twittering-on-2009-11-20\/"},"modified":"2009-11-20T22:59:00","modified_gmt":"2009-11-21T06:59:00","slug":"twittering-on-2009-11-20","status":"publish","type":"post","link":"https:\/\/www.chesnok.com\/daily\/2009\/11\/20\/twittering-on-2009-11-20\/","title":{"rendered":"twittering on 2009-11-20"},"content":{"rendered":"<ul class=\"aktt_tweet_digest\">\n<li>michael glaesemann on visualizing data about postgres.7 places for data: analyze, host, bloat, dtrace\/systap, logs, contrib, stats #<a href=\"http:\/\/search.twitter.com\/search?q=%23pgcon09j\" class=\"aktt_hashtag\">pgcon09j<\/a> <a href=\"http:\/\/twitter.com\/selenamarie\/statuses\/5883145082\" class=\"aktt_tweet_time\">#<\/a><\/li>\n<li>@<a href=\"http:\/\/twitter.com\/Mettadore\" class=\"aktt_username\">Mettadore<\/a> yes, definitely. <a href=\"http:\/\/twitter.com\/Mettadore\/statuses\/5898732486\" class=\"aktt_tweet_reply\">in reply to Mettadore<\/a> <a href=\"http:\/\/twitter.com\/selenamarie\/statuses\/5901169868\" class=\"aktt_tweet_time\">#<\/a><\/li>\n<li>listening to @<a href=\"http:\/\/twitter.com\/stefankaltenb\" class=\"aktt_username\">stefankaltenb<\/a> talk about postgres project infrastructure team and projects #<a href=\"http:\/\/search.twitter.com\/search?q=%23pgcon09j\" class=\"aktt_hashtag\">pgcon09j<\/a> <a href=\"http:\/\/twitter.com\/selenamarie\/statuses\/5906327375\" class=\"aktt_tweet_time\">#<\/a><\/li>\n<li>listening to Greg Stark talk about forensic analysis of corrupted postgresql databases #<a href=\"http:\/\/search.twitter.com\/search?q=%23pgcon09j\" class=\"aktt_hashtag\">pgcon09j<\/a> <a href=\"http:\/\/twitter.com\/selenamarie\/statuses\/5907520613\" class=\"aktt_tweet_time\">#<\/a><\/li>\n<li>most common failure reported on the postgres mailing lists is bad memory #<a href=\"http:\/\/search.twitter.com\/search?q=%23pgcon09j\" class=\"aktt_hashtag\">pgcon09j<\/a> <a href=\"http:\/\/twitter.com\/selenamarie\/statuses\/5907589686\" class=\"aktt_tweet_time\">#<\/a><\/li>\n<li>common errors:fsync=off,full_page_writes=off,hot backups done wrong,recover to different architecture, IMMUTABLE misuse,collation #<a href=\"http:\/\/search.twitter.com\/search?q=%23pgcon09j\" class=\"aktt_hashtag\">pgcon09j<\/a> <a href=\"http:\/\/twitter.com\/selenamarie\/statuses\/5907689491\" class=\"aktt_tweet_time\">#<\/a><\/li>\n<li>.@<a href=\"http:\/\/twitter.com\/janl\" class=\"aktt_username\">janl<\/a> we can just blame hardware \ud83d\ude09 but really, some config issues should be better documented, and maybe doing it wrong should be harder. <a href=\"http:\/\/twitter.com\/janl\/statuses\/5907733257\" class=\"aktt_tweet_reply\">in reply to janl<\/a> <a href=\"http:\/\/twitter.com\/selenamarie\/statuses\/5907821591\" class=\"aktt_tweet_time\">#<\/a><\/li>\n<li>@<a href=\"http:\/\/twitter.com\/janl\" class=\"aktt_username\">janl<\/a> maybe config examples should be on a continuum: cheap\/fast\/OOC &lt;-&gt; absolute consistency <a href=\"http:\/\/twitter.com\/janl\/statuses\/5907857533\" class=\"aktt_tweet_reply\">in reply to janl<\/a> <a href=\"http:\/\/twitter.com\/selenamarie\/statuses\/5908003287\" class=\"aktt_tweet_time\">#<\/a><\/li>\n<li>@<a href=\"http:\/\/twitter.com\/stewartsmith\" class=\"aktt_username\">stewartsmith<\/a> no \ud83d\ude42 there&#39;s a data structure that gets verified &#8211; then you get errors\/warnings, but no checksum. <a href=\"http:\/\/twitter.com\/stewartsmith\/statuses\/5907957404\" class=\"aktt_tweet_reply\">in reply to stewartsmith<\/a> <a href=\"http:\/\/twitter.com\/selenamarie\/statuses\/5908131230\" class=\"aktt_tweet_time\">#<\/a><\/li>\n<li>@<a href=\"http:\/\/twitter.com\/janl\" class=\"aktt_username\">janl<\/a> LOL i could make a custom config parameter that executes a function&#8230;. <a href=\"http:\/\/twitter.com\/janl\/statuses\/5908107757\" class=\"aktt_tweet_reply\">in reply to janl<\/a> <a href=\"http:\/\/twitter.com\/selenamarie\/statuses\/5908143564\" class=\"aktt_tweet_time\">#<\/a><\/li>\n<li>greg stark demonstrating zeroing out corrupted 8k pages. yeah, we&#39;ve all done that before. #<a href=\"http:\/\/search.twitter.com\/search?q=%23pgcon09j\" class=\"aktt_hashtag\">pgcon09j<\/a> <a href=\"http:\/\/twitter.com\/selenamarie\/statuses\/5908415447\" class=\"aktt_tweet_time\">#<\/a><\/li>\n<li>@<a href=\"http:\/\/twitter.com\/snaga\" class=\"aktt_username\">snaga<\/a> oh awesome! nice to know that, and thank you! <a href=\"http:\/\/twitter.com\/snaga\/statuses\/5908296577\" class=\"aktt_tweet_reply\">in reply to snaga<\/a> <a href=\"http:\/\/twitter.com\/selenamarie\/statuses\/5908432758\" class=\"aktt_tweet_time\">#<\/a><\/li>\n<li>worried about memory errors? use ECC memory, and monitor for corrected errors. DIMMs usually have 0 or lots of errors. #<a href=\"http:\/\/search.twitter.com\/search?q=%23pgcon09j\" class=\"aktt_hashtag\">pgcon09j<\/a> <a href=\"http:\/\/twitter.com\/selenamarie\/statuses\/5908585750\" class=\"aktt_tweet_time\">#<\/a><\/li>\n<li>DRAM Errors in the Wild: A Large-Scale Field study (by Bianca Schroeder, and Eduardo Pinheiro\/Wolf-Dietrich) <a href=\"http:\/\/tr.im\/FpsO\" rel=\"nofollow\">http:\/\/tr.im\/FpsO<\/a> #<a href=\"http:\/\/search.twitter.com\/search?q=%23pgcon09j\" class=\"aktt_hashtag\">pgcon09j<\/a> <a href=\"http:\/\/twitter.com\/selenamarie\/statuses\/5908616399\" class=\"aktt_tweet_time\">#<\/a><\/li>\n<li>workaround for lack of checksum: use a FS checksum (ZFS)-only catches a subset of errors &amp; does not catch in-memory corruption. #<a href=\"http:\/\/search.twitter.com\/search?q=%23pgcon09j\" class=\"aktt_hashtag\">pgcon09j<\/a> <a href=\"http:\/\/twitter.com\/selenamarie\/statuses\/5908683115\" class=\"aktt_tweet_time\">#<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>michael glaesemann on visualizing data about postgres.7 places for data: analyze, host, bloat, dtrace\/systap, logs, contrib, stats #pgcon09j # @Mettadore yes, definitely. in reply to Mettadore # listening to @stefankaltenb talk about postgres project infrastructure team and projects #pgcon09j # &hellip; <a href=\"https:\/\/www.chesnok.com\/daily\/2009\/11\/20\/twittering-on-2009-11-20\/\">Continue reading &rarr;<\/a><\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[28],"tags":[260],"class_list":["post-1321","post","type-post","status-publish","format-standard","hentry","category-twitter","tag-tweets"],"_links":{"self":[{"href":"https:\/\/www.chesnok.com\/daily\/wp-json\/wp\/v2\/posts\/1321","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.chesnok.com\/daily\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.chesnok.com\/daily\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.chesnok.com\/daily\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.chesnok.com\/daily\/wp-json\/wp\/v2\/comments?post=1321"}],"version-history":[{"count":0,"href":"https:\/\/www.chesnok.com\/daily\/wp-json\/wp\/v2\/posts\/1321\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.chesnok.com\/daily\/wp-json\/wp\/v2\/media?parent=1321"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.chesnok.com\/daily\/wp-json\/wp\/v2\/categories?post=1321"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.chesnok.com\/daily\/wp-json\/wp\/v2\/tags?post=1321"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}