From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | tim h <timh(at)vyew(dot)com> |
Cc: | pgsql-advocacy(at)postgresql(dot)org |
Subject: | Re: db corruption pg vs mysql |
Date: | 2007-05-22 19:09:36 |
Message-ID: | 46533FF0.5040907@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
tim h wrote:
> Hi. Im running one of my apps on mysql/myisam. db size: 7mil records, 5.8Gb.
> We've had some corruption problems, somehow the mysqld service failed
> corrupted the db.
>
> For many reasons, but for this reason alone, im considering switching to
> pgsql sooner
> then planned. My question is... will this same problem happen in pgsql?
No. PostgreSQL is ACID compliant.
> Is there a way to prevent or minimize corruption due to service or
> hardware failure?
Well sure, backups, UPS, Raid battery backup...
>
> also, will the use of Transactional queries prevent corruption, or is
> that a different issue?
Transactional queries is a different issue. Read this:
http://www.fredosaurus.com/notes-db/transactions/acid.html
This is what Pg has, that MySQL (at least with myisam) does not.
Joshua D. Drake
>
> thanks.
>
> --
> Tim H
> Berkeley, CA
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2007-05-22 19:17:37 | Re: db corruption pg vs mysql |
Previous Message | Bill Moran | 2007-05-22 19:06:50 | Re: db corruption pg vs mysql |