On Thu, Aug 16, 2007 at 11:47:12AM -0400, Robert Treat wrote:
> 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.
What about the catalogs? ACID user tables don't do much good if your
catalog is hosed after a crash...
--
Decibel!, aka Jim Nasby decibel@decibel.org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
