From: Craig Ringer <craig@postnewspapers.com.au>
To: mladen.gogala@vmsinfo.com
Cc: Kyriacos Kyriacou <kyriacosk@prime-tel.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: MVCC performance issue
Date: Sun, 14 Nov 2010 08:10:56 +0800
Message-ID: <4CDF2910.8010105@postnewspapers.com.au> (raw)
In-Reply-To: <4CDEDB3A.2070606@vmsinfo.com>
References: <8BCBF9DB739F034B87FE7C7D30EAE55C240D4BC8@hqex2k.francoudi.com>
<4CDE27D7.7070706@postnewspapers.com.au>
<4CDEDB3A.2070606@vmsinfo.com>
On 11/14/2010 02:38 AM, Mladen Gogala wrote:
> Craig Ringer wrote:
>> It sounds like you're describing Oracle-style MVCC, using redo logs.
>>
>> http://blogs.sybase.com/database/2009/04/mvcc-dispelling-some-oracle-fudunderstanding-the-cost/
>>
> Craig, this is an interesting blog page, making some valid points about
> the multiversioning vs. locking. The ATM example, however, is
> unrealistic and couldn't have happened the way the author describes.
Yep, you're quite right. I was using it for its explanation of some of
the costs of MVCC as Oracle implements it, because it's surprisingly
hard to find explanations/analysis of that with some quick Google
searching. I hadn't read beyond that part.
I'd be really interested in some *good* writeups of the costs/benefits
of the various common mvcc and locking based rdbms implementations.
Thanks for posting a breakdown of the issues with that article, lest
others be mislead. Appreciated.
--
Craig Ringer
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: craig@postnewspapers.com.au, mladen.gogala@vmsinfo.com, kyriacosk@prime-tel.com
Subject: Re: MVCC performance issue
In-Reply-To: <4CDF2910.8010105@postnewspapers.com.au>
* 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