330 karma · joined May 4, 2012
host1$ while : ; do nc -l 6666 > /dev/null; done
host2$ pv /dev/zero | nc host1 6666
156MiB 0:00:17 [9.46MiB/s] [ <=> ] user@host$ less /var/log/syslog
Permission Denied
crap... $ sudo !!
sudo less /var/log/syslog
Woo! $ rm -rf somedir
rm: somedir/: Permission denied
$ fucking !!add repository.... {apt-get,yum,brew,port} install {mongodb,riak,redis}
I see little benefit in compiling any of these products from source.
Is the fact that it is written in "pure Python" really the most important thing to reenforce after the name of the product itself?
Why would I use this over established products like Riak, Redis, MongoDB, etc?
On top of this, as a heavy vi user, the main navigation keys are no longer on the home row for either Colemak or Dvorak, which means I either need to make my editing far less efficient, or remap nearly every key.
I have had many very intelligent people attempt to explain the switch to Dvorak to me, and never heard a good reason to invest the time. I am curious if folks invested the same amount of concentrated time improving their QWERTY skills (relative to the amount of time folks spend learning a new layout) if there would be a similar speed improvement.
"INSERT modifies data and structures. You should be careful with it, and test it before using it in production. You should also ensure that you have recoverable backups before using this tool."
"ALTER modifies data and structures. You should be careful with it, and test it before using it in production. You should also ensure that you have recoverable backups before using this tool."
It's just good advice to test stuff before you use it in production. Discarding an awesome product simply because the authors (responsibly) mention that you should probably test it out seems overly paranoid and would severely limit your choices. Percona Toolkit is the most well known and reliable set of tools out there in the MySQL ecosystem.
According to the Square App, I have to drive 11 miles away to find the nearest accepted location.
Ultimately, I think both will operate in parallel for quite some time until Apple decides to release something and takes over the world of payments overnight. :)
Riak is written in Erlang.
Slony, in a word, is awful. It's probably as good as it can be given the limitations of working within a trigger-based world, but in the 3 years I spent maintaining Slony clusters, I lost count of the number of times that I had to take a site offline (sometimes for hours) in order to rebuild from scratch because of a failed schema change. Many times, I was able to recover by careful manipulation of the sl_events table, but far too frequently, the error was unrecoverable. Slony is slow, unreliable, not tolerant of high latency connections, and fragile. It was always one of my greatest frustrations that the PostgreSQL community saw it as a solution given how completely unreliable it is. Perhaps things have changed in the 2 years since I last touched it, but I am skeptical.
Please try to understand that my few objections to PostgreSQL come from actual real world experience with both MySQL and PostgreSQL, not from reading blog posts. Both products have great features as well as unpolished turds...it's just a matter of deciding which color of poop you are willing to clean out of the diaper. :)