Re: MVCC and Implications for (Near) Real-Time Application

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <pgsql-performance(at)postgresql(dot)org>, "Steve Wong" <powerpchead(at)yahoo(dot)com>
Subject: Re: MVCC and Implications for (Near) Real-Time Application
Date: 2010-10-29 17:18:20
Message-ID: 4CCABB8C0200002500036F8D@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Steve Wong <powerpchead(at)yahoo(dot)com> wrote:

> (1) Does the MVCC architecture introduce significant delays
> between insert by a thread and visibility by other threads (I am
> unclear about how multiple versions are "collapsed" or reconciled,
> as well as how different query threads are seeing which version)?

As soon as the inserting transaction commits the inserted row is
visible to new snapshots. If you are in an explicit transaction the
commit will have occurred before the return from the COMMIT request;
otherwise it will have completed before the return from the INSERT
request.

You will get a new snapshot for every statement in READ COMMITTED
(or lower) transaction isolation. You will get a new snapshot for
each database transaction in higher isolation levels.

-Kevin

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2010-10-29 17:48:18 Re: typoed column name, but postgres didn't grump
Previous Message A.M. 2010-10-29 17:05:48 Re: MVCC and Implications for (Near) Real-Time Application