Skip site navigation (1) Skip section navigation (2)

Re: Possible Commit Syntax Change for Improved TPS

From: seunosewa(at)inaira(dot)com (Seun Osewa)
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Possible Commit Syntax Change for Improved TPS
Date: 2003-10-02 12:31:52
Message-ID: ba87a3cf.0310020431.366bb6c9@posting.google.com (view raw or flat)
Thread:
Lists: pgsql-hackers
tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) wrote in message news:<19310(dot)1064932466(at)sss(dot)pgh(dot)pa(dot)us>...
> Christopher Browne <cbbrowne(at)acm(dot)org> writes:
> > In the last exciting episode, seunosewa(at)inaira(dot)com (Seun Osewa) wrote:
> > So I want to ask, "what if databases have a 'COMMIT NOSYNC;' option?" 
> > Another possibility in this would be to have not one, but TWO
> > backends.  
> > One database, on one port, is running in FSYNC mode, so that the
> > "really vital" stuff is sure to get committed quickly.  The other, on
> > another port, has FSYNC turned off in its postgresql.conf file, and
> > the set of "untrusted" files go there.
> They would have in fact to be two separate installations (not two
> databases under one postmaster).  There is no way to make some
> transactions less safe than others in a single installation, because
> they're all hitting the same WAL log, and potentially modifying the
> same disk buffers to boot.  Anyone's WAL sync therefore syncs everyone's
> changes-so-far.
The beauty of the scheme is that the WAL syncs which "sync everyone's 
changes so far" would cost about the same as the WAL syncs for just 
one transaction being committed.  But when there are so many trans-
actions we would not have to sync the WAL so often.

Seun Osewa

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2003-10-02 14:16:30
Subject: Re: minor view creation weirdness
Previous:From: Rod TaylorDate: 2003-10-02 12:28:08
Subject: Re: Thoughts on maintaining 7.3

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group