Re: MVCC and Implications for (Near) Real-Time Application - Mailing list pgsql-performance

From Kevin Grittner
Subject Re: MVCC and Implications for (Near) Real-Time Application
Date
Msg-id 4CCABB8C0200002500036F8D@gw.wicourts.gov
Whole thread Raw
In response to MVCC and Implications for (Near) Real-Time Application  (Steve Wong <powerpchead@yahoo.com>)
List pgsql-performance
Steve Wong <powerpchead@yahoo.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

pgsql-performance by date:

Previous
From: "A.M."
Date:
Subject: Re: MVCC and Implications for (Near) Real-Time Application
Next
From: Tom Lane
Date:
Subject: Re: typoed column name, but postgres didn't grump