Comments on: Good Error Recovery is Hard, So Use PostgreSQL http://thoughts.j-davis.com/2009/12/23/good-error-recovery-is-hard-so-use-postgresql/ Ideas on Databases, Logic, and Language by Jeff Davis Sat, 10 Jul 2010 14:36:49 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Goldpreis http://thoughts.j-davis.com/2009/12/23/good-error-recovery-is-hard-so-use-postgresql/comment-page-1/#comment-232 Goldpreis Sat, 03 Jul 2010 17:52:39 +0000 http://thoughts.j-davis.com/?p=221#comment-232 Thanks Jeff Davis.Good post. Thanks Jeff Davis.Good post.

]]> By: Jeff Davis http://thoughts.j-davis.com/2009/12/23/good-error-recovery-is-hard-so-use-postgresql/comment-page-1/#comment-171 Jeff Davis Wed, 30 Dec 2009 02:58:12 +0000 http://thoughts.j-davis.com/?p=221#comment-171 “fsync = off” can (and probably will) cause corruption on any platform, not just OSX. It’s well-documented that it’s dangerous. PostgreSQL + OSX should be fine. “fsync = off” can (and probably will) cause corruption on any platform, not just OSX. It’s well-documented that it’s dangerous.

PostgreSQL + OSX should be fine.

]]> By: Symbiatch http://thoughts.j-davis.com/2009/12/23/good-error-recovery-is-hard-so-use-postgresql/comment-page-1/#comment-169 Symbiatch Mon, 28 Dec 2009 05:06:03 +0000 http://thoughts.j-davis.com/?p=221#comment-169 I totally agree with you on this one. I've been using Pgsql for a decade now and I've always loved the fact that it doesn't die on me. Ever. Even if there's a power outage during updates to the database, disk space runs out, OOM or whatever. Never had a single fault in the databases, even in the ones running tens of gigabytes of data and being updated while these conditions appear. Naturally the servers are one thing, in production use running out of disk space or sudden power outage without memory backup in the disk controllers mustn't happen (but they nevertheless do sometimes), but on the test systems these have happened so many times. The only way I've gotten Pgsql to corrupt itself has been on OS X. fsync off, running long and hard updates and then having the OS or something crash and then it's bye bye for that database. Dunno if the OS X port is not that good or if it's just that HFS+ doesn't really cut it. Fortunately I don't have to use OS X, I can work with decent OSs :) I totally agree with you on this one. I’ve been using Pgsql for a decade now and I’ve always loved the fact that it doesn’t die on me. Ever. Even if there’s a power outage during updates to the database, disk space runs out, OOM or whatever. Never had a single fault in the databases, even in the ones running tens of gigabytes of data and being updated while these conditions appear.

Naturally the servers are one thing, in production use running out of disk space or sudden power outage without memory backup in the disk controllers mustn’t happen (but they nevertheless do sometimes), but on the test systems these have happened so many times.

The only way I’ve gotten Pgsql to corrupt itself has been on OS X. fsync off, running long and hard updates and then having the OS or something crash and then it’s bye bye for that database. Dunno if the OS X port is not that good or if it’s just that HFS+ doesn’t really cut it. Fortunately I don’t have to use OS X, I can work with decent OSs :)

]]> By: Jeff Davis http://thoughts.j-davis.com/2009/12/23/good-error-recovery-is-hard-so-use-postgresql/comment-page-1/#comment-168 Jeff Davis Thu, 24 Dec 2009 20:58:20 +0000 http://thoughts.j-davis.com/?p=221#comment-168 Yes, I removed the offensive comment. Until now, offensive comments were not a problem. If it becomes a problem, I'll enable moderation. Yes, I removed the offensive comment. Until now, offensive comments were not a problem. If it becomes a problem, I’ll enable moderation.

]]> By: Raoul Duke http://thoughts.j-davis.com/2009/12/23/good-error-recovery-is-hard-so-use-postgresql/comment-page-1/#comment-167 Raoul Duke Thu, 24 Dec 2009 20:17:44 +0000 http://thoughts.j-davis.com/?p=221#comment-167 oh now what i was referring to has disappeared, so i guess there is some editing going on. re: the actual meat of the story: i used mysql before (probably like 3 years ago now) and at the time it really did seem to suck when it came to error recovery e.g. rollback. it amazes me that people want to use a rdbms and yet don't seem to want it to be solid. oh now what i was referring to has disappeared, so i guess there is some editing going on.

re: the actual meat of the story: i used mysql before (probably like 3 years ago now) and at the time it really did seem to suck when it came to error recovery e.g. rollback. it amazes me that people want to use a rdbms and yet don’t seem to want it to be solid.

]]> By: Raoul Duke http://thoughts.j-davis.com/2009/12/23/good-error-recovery-is-hard-so-use-postgresql/comment-page-1/#comment-166 Raoul Duke Thu, 24 Dec 2009 20:16:04 +0000 http://thoughts.j-davis.com/?p=221#comment-166 @retard hm, maybe Mr. Davis should enable comment moderation... @retard

hm, maybe Mr. Davis should enable comment moderation…

]]>