pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: mladen.gogala@vmsinfo.com
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: Sun, 10 Oct 2010 13:45:01 +0200
Message-ID: <871v7y2rwi.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <4CB0E006.8010905@vmsinfo.com>
References: <AANLkTimNJc=0ffgRO_gO6Vsq06=aqBYXZouhbv0kBe-i@mail.gmail.com>
	<4CAE3FDB.1040909@2ndquadrant.com>
	<87ocb3yu10.fsf@mid.deneb.enyo.de>
	<4CB0E006.8010905@vmsinfo.com>

* Mladen Gogala:

> 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.

That's a bit over the top.  It may make sense to use PostgreSQL even
if the file system doesn't guarantuee ACID by keeping multiple
checksummed copies of the database files.  Asynchronous commits offer
yet another trade-off here.

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.



view thread (17+ messages)  latest in thread

Message-ID: <871v7y2rwi.fsf@mid.deneb.enyo.de>
Permalink:  ../871v7y2rwi.fsf@mid.deneb.enyo.de/
Also on:    postgresql.org/message-id/871v7y2rwi.fsf@mid.deneb.enyo.de

 · 

reply

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: fw@deneb.enyo.de, mladen.gogala@vmsinfo.com, greg@2ndquadrant.com, synfinatic@gmail.com
  Subject: Re: large dataset with write vs read clients
  In-Reply-To: <871v7y2rwi.fsf@mid.deneb.enyo.de>

* 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