From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | pgsql-advocacy(at)postgresql(dot)org |
Cc: | "vincent" <vinny(at)xs4all(dot)nl> |
Subject: | Re: 12 Silver Bullets |
Date: | 2007-08-16 15:47:12 |
Message-ID: | 200708161147.13202.xzilla@users.sourceforge.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
On Thursday 16 August 2007 03:46, vincent wrote:
> > On Thu, 16 Aug 2007, Simon Riggs wrote:
> >>> 2. Robust transactional ACID behavior under all circumstances
> >>
> >> Async commit changes that, since it relaxes the Durability aspect.
> >
> > And one can wreak havoc right now if you turn fsync off. Maybe the
> > wording may need to be tweaked here. The disclaimer in the detailed
> > document is "barring hardware failure or grossly improper configuration".
> > If you expected ACID, but used Async commit, that certainly falls into
> > the improper configuration category.
>
> Does the reader really need to know so many details in a list like this?
>
> PgSQL defaults to ACID, which is the point I'd like to make in a list like
> this; the user does not have to do anything special to get ACID, unlike
> some databases who shall rename nameless...
>
The windows default table type for mysql is innodb, which is ACID. Since > 50%
of thier users work on windows (perhaps not deploy, but do
development/testing) this means that most of them are getting ACID out of the
box as well.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Bob Zurek | 2007-08-16 15:49:50 | Re: 12 Silver Bullets |
Previous Message | Rodrigo De León | 2007-08-16 15:12:50 | Oracle 11g |