Terrific. Now this is what I was looking for...a starting point along
with validation. Sorry if I wasn't clear enough in the first email.
Thanks Greg for taking the first crack and others for this feedback.
Z.
-----Original Message-----
From: pgsql-advocacy-owner@postgresql.org
[mailto:pgsql-advocacy-owner@postgresql.org] On Behalf Of vincent
Sent: Thursday, August 16, 2007 3:46 AM
To: pgsql-advocacy@postgresql.org
Subject: Re: [pgsql-advocacy] 12 Silver Bullets
> 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...
Sure a user can force non-acid behaviour, that's not what you want to
put
forward when promoting PgSQL. It's the truth, but it's too much
information.
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match