Category Archives: twitter

twitter

Weekly tweet digest for 2011-05-22

  • Contemplating odd note left by a neighbor reminding me I am loved paired with flowers taken from my yard. http://yfrog.com/gzxmljcpj #
  • The other side has foil stickers and <3s from the universe on it http://yfrog.com/h7oh7cjj #
  • #pgcon day 0 http://chesnok.com/u/29 #postgres #
  • Discussing whether global deadlocks are inevitable in multi-master replication #pgcon #clusteringsummit #
  • OH: "Order of commit is not the same thing as apparent order of execution. And we don't want to get into that right now." #pgcon #
  • having to remind myself that i don't need to correct people that are wrong on the internet. #
  • lovely meeting a few new faces, hearing ppl's impressions of portlandia and now turning in early the night before developer meeting #pgcon #
  • We still have a few more openings for lightning talks! Submit yours!! http://chesnok.com/u/1Z #pgcon #
  • OH: "If you think of it as a local data wrapper, it makes more sense." #pgcon #
  • OH: "We've now fixed our problem of being ahead of schedule." #
  • Just updated the commitfest application for the 9.2 development season. Guess that makes it officiall! https://commitfest.postgresql.org/ #
  • Looking at http://reorg.projects.postgresql.org/index.html #pgcon #
  • OH: "User-defined demons." #advancedfeatures #
  • mmm. scotch. #
  • Next year, @magnushagander is in charge of weather. That means rain again #pgcon #
  • Watching @pramsey keynote at #pgcon http://flic.kr/p/9JX9Ds #
  • "another thing for Canadians to be smug about. We invented GIS!" (re the Canada Land Inventory) -@pramsey #pgcon #
  • Announcing Postgres Open! September 14-16 in Chicago http://chesnok.com/u/2c #
  • "PostGIS is our biggest, highest profile third-party extension" that pushes the limits of Postgres #pgcon #
  • oops, we've all been talking about @pwramsey #pgcon #
  • Now @pwramsey sharing why PostGIS didn't need to be part of Postgres, but could operate well as an external extension. #pgcon #
  • "another thing for Canadians to be smug about. We invented GIS!" (re the Canada Land Inventory) -@pwramsey #pgcon #
  • +1 RT @robertmhaas: Scalability patterns: "New nodes are never free." -@robtreat2 #pgcon #
  • Lightning talks are looking awesome (5:30pm today!) #pgcon #
  • Updated PL Summit meeting agenda http://wiki.postgresql.org/wiki/PgCon_2011_PL_Summit#Tentative_Agenda #pgcon #
  • Getting ready for my talk http://www.pgcon.org/2011/schedule/events/366.en.html #pgcon #
  • Woo! Got a patch committed http://chesnok.com/u/2d #pgcon #postgres #
  • Almost time for lightning talks. First talk includes a live demo. In 5 minutes. Will it work? #danger #pgcon #
  • We will post all the lightning talk slides on the Postgres wiki in the morning. Now, to the party! #pgcon #
  • Lightning talks mostly uploaded (except the CBC talk that was slightly too large… working on it 🙂 http://chesnok.com/u/2e #
  • Just heard from someone planning a 1 million table postgres instance. #pgcon #
  • SSI (serializable snapshot isolation) has never been implemented in production in another database. #postgres #pgcon #
  • "And therefore transaction one is its own grandfather.. and that just doesn't work." #pgcon #ssi #
  • "The people who wrote the SQL standard got this wrong. They got it wrong more than once." #ssi #pgcon #
  • pro-tip: a read-only transaction can create a cycle of dependencies that make a transaction sequence not serializable. #pgcon #
  • Basic idea: find a cycle in a graph, and break the transaction that caused it to preserve serializability. #ssi #pgcon #hopeigotthatright #
  • SSI rule is: don't let a transaction both have a rw-conflict *in* AND a rw-conflict *out* #ssi #pgcon #
  • SIREAD locks don't cause blocking (predicate locks are just flags). And they can persist beyond transaction commit. #pgcon #ssi #
  • Agenda for tomorrow's Procedural Language summit http://wiki.postgresql.org/wiki/PgCon_2011_PL_Summit #pgcon #
  • Almost the end of #pgcon 🙁 #
  • "If it was hard to write it should be hard to use." -Jan Wieck #slony #pgcon #
  • "I don't want to have anything that says "release it" on the back." #janwieck #pgcon #
  • Enjoying @3dmashup's slides on PL/OpenCL, causing lots of conversation #pgcon #plsummit #
  • Great opening slides giving state-of PL/Python, status of PL/Perl, PL/TCL and PL/Lua. Next up PL/PHP! #pgcon #plsummit #
  • We're at Patty Bolands Pub #pgcon #
  • We're doing CREATE TABLE timetrials #pgcon #pubtrack #
  • Pubtrack #pgcon http://flic.kr/p/9KwiBF #
  • More details on the pubtrack at #pgcon http://chesnok.com/u/2i #
twitter

twittering on 2011-05-21

  • Lightning talks mostly uploaded (except the CBC talk that was slightly too large… working on it 🙂 http://chesnok.com/u/2e #
  • Just heard from someone planning a 1 million table postgres instance. #pgcon #
  • SSI (serializable snapshot isolation) has never been implemented in production in another database. #postgres #pgcon #
  • "And therefore transaction one is its own grandfather.. and that just doesn't work." #pgcon #ssi #
  • "The people who wrote the SQL standard got this wrong. They got it wrong more than once." #ssi #pgcon #
  • pro-tip: a read-only transaction can create a cycle of dependencies that make a transaction sequence not serializable. #pgcon #
  • Basic idea: find a cycle in a graph, and break the transaction that caused it to preserve serializability. #ssi #pgcon #hopeigotthatright #
  • SSI rule is: don't let a transaction both have a rw-conflict *in* AND a rw-conflict *out* #ssi #pgcon #
  • SIREAD locks don't cause blocking (predicate locks are just flags). And they can persist beyond transaction commit. #pgcon #ssi #
  • Agenda for tomorrow's Procedural Language summit http://wiki.postgresql.org/wiki/PgCon_2011_PL_Summit #pgcon #
  • Almost the end of #pgcon 🙁 #
  • "If it was hard to write it should be hard to use." -Jan Wieck #slony #pgcon #
  • "I don't want to have anything that says "release it" on the back." #janwieck #pgcon #
twitter

twittering on 2011-05-20

twitter

twittering on 2011-05-18

  • Discussing whether global deadlocks are inevitable in multi-master replication #pgcon #clusteringsummit #
  • OH: "Order of commit is not the same thing as apparent order of execution. And we don't want to get into that right now." #pgcon #
  • having to remind myself that i don't need to correct people that are wrong on the internet. #
  • lovely meeting a few new faces, hearing ppl's impressions of portlandia and now turning in early the night before developer meeting #pgcon #
  • We still have a few more openings for lightning talks! Submit yours!! http://chesnok.com/u/1Z #pgcon #
twitter

Weekly tweet digest for 2011-05-15