[Gllug] Introductions to Databases

[Grzegorz Jaskiewicz]

On 16 Jul 2009, at 18:19, Bruce Richardson wrote:

> On Thu, Jul 16, 2009 at 06:01:10PM +0100, - wrote:
>>
>> You're wrong. I want reliable database storage. Anything else
>> (*everything* else) is secondary. What's the point of replication and
>> other fancy features if you can't be sure that the data you put into
>> your database will be the same as the data you get back out? I may  
>> not
>> care about the purity of the code (although it's usually a good
>> indicator that they're doing things right), but I certainly care  
>> about
>> the integrity of my data. *You* may not care. And that's fine. But
>> don't assume that everyone else feels the same.
>
> I agree, but let's not pretend that Postgresql makes a religion of
> data purity; historically, it was the correctness and  
> comprehensiveness
> of the SQL implementation that the postgres development community  
> cared
> about; not only did performance come quite a distant second, so did  
> data
> integrity.  It's not *that* long ago that a chunk of the user base  
> were
> seeing regular data corruption issues with Postgresql.

and was that ever reported to postgresql hackers ?
Cos most of those usually come from hardware problems.
On contrary, if you run out of space mysql will corrupt your data.  
(unless they fixed that). Etc, etc.
Try running mysql database, keep it busy, and keep pulling a plug on  
that server.
Not to mention funny SQL syntax that mysql allows, that can cause  
problems. ...

Not to say, that postgresql is bug free, and wears white coat. But is  
much better on safety and reliability side IMO.

But at the end of a day, everyone has something called free will. So  
you are free to choose whatever you want, in particular what suits you  
best, and provides solution to your problem.


-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug