Links
Want to work with me at the $DAYJOB?
I am the CEO of OmniTI where I do all sorts of stuff I find absolutely fascinating.
Writing
I spent a few years writing down my thoughts about how one should approach problems. If you're looking for a how-to guide, a cookbook, or a reference this book is not for you. If you want to learn by challenging the way you think, pick up a copy.
Hacking
It is rumored that I write code sometimes. I often don't believe this myself, so I use this to follow what it is that I'm working on:
You need to upgrade your Flash Player
Categories
Recent Entries
- ZFS and Zetaback win again
- Friday, June 18 2010
- Surge: scalability matters
- Friday, June 4 2010
- Vibram Four Fingers: Syndactyly Successful
- Sunday, May 23 2010
- Plan Wagon
- Monday, May 10 2010
- pg_controldata from SQL
- Thursday, April 29 2010
- from pcap to postgres: forensic performance analysis
- Friday, April 2 2010
- pg_amqp slides from PgEast2010
- Tuesday, March 30 2010
- Thoughts on the cloud
- Tuesday, March 23 2010
- Managing risk by deploying incessantly
- Thursday, March 18 2010
- Squeezing precise numbers into fixed width types... or faking it
- Friday, March 5 2010
Sunday, August 23. 2009 at 09:03 (Link) (Reply)
Looks, yes. But it's not, it's heavily broken.
Take a look at the issues: http://github.com/rubyrep/rubyrep/issues -- some of this stuff is hilarious (like, re-creating the triggers instead of using "alter table disable trigger all").
The author is not responding; see also the closed-but-not-resolved issues.
Thursday, August 27. 2009 at 06:25 (Link) (Reply)
As the developer of rubyrep: thanks for checking out this software.
A few points which I would like to clarify:
I am not "not responding". As announced on the rubyrep mailling list, I was on vacation for 2.5 weeks. Now I am back. I look forward to look at your raised issues in the coming days.
Regarding my "hilarious" recreating of triggers instead of using "disable trigger":
Just disabling the trigger, that would be nice.
Unfortunately disabling the triggers locks the complete table. For that reason I cannot use it. On top of that, rubyrep provides replication functionality for both PostgreSQL and MySQL. MySQL doesn't even have a 'disable trigger' functionality. Let's continue that discussion on the according issue page. If there is a clean and simple solution for this somewhere, I would be happy to implement it.
Regarding closed but not resolved issues
I strive to only close unresolved issues if there is a good reason for it. I am stating that reason in the closure message. It is of course possible that my reasoning is incorrect. In that case please comment / re-open and we will look for a solution together.
Best Regards,
Arndt Lehmann
(I wish I could format this message...)