From: Mladen Gogala <mladen.gogala@vmsinfo.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Greg Smith <greg@2ndquadrant.com>
Cc: Aaron Turner <synfinatic@gmail.com>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: large dataset with write vs read clients
Date: Sat, 09 Oct 2010 17:35:02 -0400
Message-ID: <4CB0E006.8010905@vmsinfo.com> (raw)
In-Reply-To: <87ocb3yu10.fsf@mid.deneb.enyo.de>
References: <AANLkTimNJc=0ffgRO_gO6Vsq06=aqBYXZouhbv0kBe-i@mail.gmail.com>
<4CAE3FDB.1040909@2ndquadrant.com>
<87ocb3yu10.fsf@mid.deneb.enyo.de>
I have a logical problem with asynchronous commit. The "commit" command
should instruct the database to make the outcome of the transaction
permanent. The application should wait to see whether the commit was
successful or not. Asynchronous behavior in the commit statement breaks
the ACID rules and should not be used in a RDBMS system. If you don't
need ACID, you may not need RDBMS at all. You may try with MongoDB.
MongoDB is web scale: http://www.youtube.com/watch?v=b2F-DItXtZs
Florian Weimer wrote:
> * Greg Smith:
>
>
>> Given the size of your database, I'd advise you consider a migration
>> to a new version ASAP. 8.4 is a nice stable release at this point,
>> that's the one to consider moving to.
>>
>
> It also offers asynchronous commits, which might be a good tradeoff
> here (especially if the data gathered is not used for billing purposes
> 8-).
>
>
--
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, fw@deneb.enyo.de, greg@2ndquadrant.com, synfinatic@gmail.com
Subject: Re: large dataset with write vs read clients
In-Reply-To: <4CB0E006.8010905@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