From: Mladen Gogala <mladen.gogala@vmsinfo.com>
To: pgsql-performance@postgresql.org
Subject: Re: large dataset with write vs read clients
Date: Sun, 10 Oct 2010 11:29:49 -0400
Message-ID: <4CB1DBED.70607@vmsinfo.com> (raw)
In-Reply-To: <871v7y2rwi.fsf@mid.deneb.enyo.de>
References: <AANLkTimNJc=0ffgRO_gO6Vsq06=aqBYXZouhbv0kBe-i@mail.gmail.com>
<4CAE3FDB.1040909@2ndquadrant.com>
<87ocb3yu10.fsf@mid.deneb.enyo.de>
<4CB0E006.8010905@vmsinfo.com>
<871v7y2rwi.fsf@mid.deneb.enyo.de>
On 10/10/2010 7:45 AM, Florian Weimer wrote:
> Some people use RDBMSs mostly for the*M* part, to get a consistent
> administration experience across multiple applications. And even with
> asynchronous commits, PostgreSQL will maintain a consistent state of
> the database.
Both Postgres and Oracle have that option and both databases will
maintain the consistent state, but both databases will allow the loss of
data in case of system crash. Strictly speaking, that does break the
"D" in ACID.
--
Mladen Gogala
Sr. Oracle DBA
1500 Broadway
New York, NY 10036
(212) 329-5251
www.vmsinfo.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mladen.gogala@vmsinfo.com
Subject: Re: large dataset with write vs read clients
In-Reply-To: <4CB1DBED.70607@vmsinfo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox