twittering on 2008-05-22

  • @gorthx happy birthday! #
  • @br3nda i don’t! but i will see if i can track one down here. #
  • i may have gotten one twitter convert this evening. pg folks keep asking me how it is different from IRC. i ask them where the RSS feed is. #
  • @SharonG you crazy! #
  • @PortlandPolice might be into this postgres talk – http://is.gd/k3e – if they were into that sort of thing. #
  • @markwkm i love cutting my own mats. #
  • @petdance whatevs! excuses! #
  • @Crad I’m going to use that one tomorrow! #
  • so sleepy. @Crad: you’re on! c u in the morning. #
  • Headed out 4 breakfast #pgcon #
  • watching bruce momjian give the keynote at #pgcon #
  • if you’re interested in more #pgcon coverage, follow @crad, @franciscojunior and @fuzzychef #
  • there were 26 people at the postgresql developer meeting yesterday, many of whom have been part of the project for 7 years or more #pgcon #
  • in andrew sullivan’s talk about postgresql development and project management #
  • lots of software development is about taste. so arguments happen about ‘ugly code’ #pgcon #
  • alan cox: by the time the code is written you already need the feature. OSS is always late! (OLS keynote from 1999) #pgcon #
  • just got info for a cool postgres community announcement, more this afternoon! #
  • a. sullivan sez postgresql core code is good, good ansi compliance and good code review (although we need more reviewers!) #pgcon #
  • “postgresql is code with a bald spot, it’s getting old!” a. sullivan #pgcon #
  • “postgres needs users…” some companies are willing to implement features that we may not want, but lots of users want them #pgcon #
  • wishing @eggyknap could be in ottawa! you could be giving me a lolcode tutorial on all the new features 😉 #
  • if we started the pgsql-roadmap mailing list, it would be a flamewar #pgcon #
  • part of what makes the project is good is that flamewars are avoided – maybe because we avoid big, vague feature discussions #pgcon #
  • @fuzzychef oh, it’s not so bad! better tools!! #
  • in horizontal scalability with postgresql by jack orenstein from Hitachi #pgcon #
  • talk is about a fixed content storage system, HCAP, originally created by Archivas #
  • @Crad great minds think alike 😉 #
  • jack’s architecture overview slide says “not drawn to scale” #pgcon #
  • @aurynn that is some serious twinsight! 😉 #
  • @aurynn wish you were here at pgcon. i’ve been chatting with others about how twitter has filled a void many of us have had re: peers #
  • @Crad @fuzzychef you should all follow @hashtags and mark your tweets with #pgcon #
  • @Crad @fuzzychef then your posts will show up here http://www.hashtags.org/tag/pgcon/ #
  • in susanne ebrecht’s “what postgresql could learn from mysql” talk #pgcon #
  • how did mysql get market share? early versions available on windows, great interoperability with PHP #pgcon #
  • loving the eierlegende wollmilchsau in susanne’s slides #pgcon #
  • @theory OMG. i never realized @petdance was trying to be a moose. *slapping forehead* #
  • i don’t agree that marketing is an attempt to sell bugs as features 😉 #pgcon #
  • in synchronous log shipping replication by ITAGAKI Takahiro #pgcon #
  • had a great convo with @decibel about tracking user questions and problems on pgsql-general and the irc channel #
  • oh cool! the NTT guys are talking about releasing their log shipping tools as open source modules for postgresql #pgcon #
  • @xolotl try http://is.gd/kr6 #
  • in magnus hagander’s search.postgresql.org talk #pgcon #
  • Retweeting @amyrsward: WomenWhoTech Portland Potluck Picnic in the Park! 6/22, 11 – 2. Mark your calendars, ladies! http://snurl.com/2a5ek #
  • used PHP for http://www.postgresql.org because you can totally ignore encodings #pgcon #
  • @verso you totally can! i wish they had an upcoming event instead of facebook, but maybe we can just put it in the Calagator 😉 #
  • search.postgresql.org doesn’t map email addresses, but you can search on full names from the email headers #pgcon #
  • @amyrsward is it cool if we put the event in the calagator? #
  • @theory yeah, they are broken. but i think that there are too many pages that are broken to bother fixing it. #
  • @theory but we’re volunteers! 😉 #
  • lightning talks were awesome!! #pgcon going to enterprisedb party shortly. #