grepmymind.com
Events - Grep My Mind
http://www.grepmymind.com/topics/events
Wonder what’s on my mind? Grep -ls ‘what the…? 8217; *.blog. Welcome to Grep My Mind. Feel free to grope and grep your way through my thoughts on technology, the Internet, PHP, and other random particles of knowledge. My randomness is my own and not those of any company that I may or may not be working for at some point. I may be right, I may be wrong, but as Deep Thought said, "42.". How FriendFeed uses MySQL to store schema-less data – SF MySQL Meetup April 6th, 2009. When: 6:30pm Monday April 6th, 2009.
strategicmessaging.com
Should you start a tech company? | Strategic Messaging
http://www.strategicmessaging.com/should-you-start-a-tech-company/2015/04/24
April 24, 2015. Should you start a tech company? I occasionally get very hands-on in accelerating a raw start-up. Typically this is when an engineer comes to me with an unquestionably clever idea and asks me — sometimes in very broken English. 8212; whether and how he can get rich from it. So let’s collect some thoughts on the subject. A start-up product idea needs to satisfy multiple criteria. Awkwardly, they’re rather contradictory to each other. 8230; but which much larger potential competitors cannot.
nicholasgoodman.com
DynamoBI is dead, long live LucidDB! | Goodman on BI
http://www.nicholasgoodman.com/bt/blog/2012/10/08/dynamobi-is-dead
Thoughts on Open Source, Analytics. About this Data Dynamo and BI Geek. DynamoBI is dead, long live LucidDB! To our Partners, Employees, Customers, Friends, and Community:. It is my unfortunate duty to inform all of you that DynamoBI is ceasing commercial operations October 31, 2012;. We started DynamoBI 3 years ago when we saw our most favorite open source project, LucidDB, finding limited prospects for adoption without a growth to full, commercial support which many (most! 2) Open Source price points a...
database-explorer.blogspot.com
Database Explorer: August 2011
http://database-explorer.blogspot.com/2011_08_01_archive.html
Wednesday, 17 August 2011. R is for Innovation. I'm pleased to note that Teradata just announced a plugin for the R language. As many of you will know, PostgreSQL has supported server functions written in the R language for many years. So its good that Teradata has seen the light at last and by doing so has validated the innovations that PostgreSQL has made. That pretty much is the complete set. Cool. Well, almost. Let's wait and see what happens when the VC runs out. Links to this post. An Ending and a ...
database-explorer.blogspot.com
Database Explorer: June 2011
http://database-explorer.blogspot.com/2011_06_01_archive.html
Thursday, 16 June 2011. In High Availability we talk about "Five Nines" meaning 99.999% availability. I like to joke that a badly configured system has "Nine Fives" availability or 55.555555% availability. With a sensible architecture and good operational controls, data can be made "Five Nines" safe with PostgreSQL 9.1. I was reminded today that "Five Nines" had another meaning in an earlier age. Wilfrid Owen's wartime poetry describes. And towards our distant rest began to trudge. Links to this post.
database-explorer.blogspot.com
Database Explorer: July 2011
http://database-explorer.blogspot.com/2011_07_01_archive.html
Tuesday, 19 July 2011. Cascading Replication is now part of PostgreSQL 9.2, thanks to Fujii Masao. The idea is that a streaming replication standby can also stream data onto other standbys. This allows a complex network of interrelated servers to fulfil the roles of High Availability, High Durability, Distributed data access capacity and Reporting requirements. You can set up chained configurations like A - B - C. Or more complex arrangements like. Links to this post. The most amazing thing were the comm...
database-explorer.blogspot.com
Database Explorer: January 2013
http://database-explorer.blogspot.com/2013_01_01_archive.html
Wednesday, 23 January 2013. Reducing Contention with Foreign Key Locks. PostgreSQL's Foreign Key support underpins our ability to enforce data quality in the database. A feature known as "Referential Integrity"allows us to link relational tables together to ensure the values in each table match. The solution was a relatively simple idea: just lock the key value, not the whole row. That allows UPDATEs to proceed and application contention to be reduced in many cases. Development took more than 2 years, wi...
database-explorer.blogspot.com
Database Explorer: Where lies the truth?
http://database-explorer.blogspot.com/2014/10/where-lies-truth.html
Thursday, 30 October 2014. Where lies the truth? Ben Bradlee, the former editor of the Washington Post died recently. A famous speech of his from 1997 contains some words that mean something for me. It starts like this. Newspapers don't tell the truth under many different, and occasionally innocent, scenarios. Mostly when they don't know the truth. Or when they quote someone who does not know the truth. And finally, when they quote someone who is flat out lying.". Where lies the truth? Database Architect...
database-explorer.blogspot.com
Database Explorer: June 2010
http://database-explorer.blogspot.com/2010_06_01_archive.html
Thursday, 24 June 2010. Hot Bugs and Cold Beer. 2ndQuadrant is sponsoring a number of Bugs and Beer events at PostgreSQL user groups around the world. The idea is to get together with your friends and see if we can shake out any more bugs in Hot Standby prior to release. Particular focus on these areas:. Transactions holding locks before/during/after base backup taken. Any other ways you can find to break it. Please write to me at simon@2ndQuadrant.com if you'd like funding for a local event. Originally ...
database-explorer.blogspot.com
Database Explorer: Reducing Contention with Foreign Key Locks
http://database-explorer.blogspot.com/2013/01/reducing-contention-with-foreign-key.html
Wednesday, 23 January 2013. Reducing Contention with Foreign Key Locks. PostgreSQL's Foreign Key support underpins our ability to enforce data quality in the database. A feature known as "Referential Integrity"allows us to link relational tables together to ensure the values in each table match. The solution was a relatively simple idea: just lock the key value, not the whole row. That allows UPDATEs to proceed and application contention to be reduced in many cases. Development took more than 2 years, wi...
SOCIAL ENGAGEMENT