Re: A long-running transaction

From: Joe <dev(at)freedomcircle(dot)net>
To: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: A long-running transaction
Date: 2007-04-13 16:42:36
Message-ID: 1176482556.782.83.camel@pampa
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Hi Andrew,

On Fri, 2007-04-13 at 07:49 -0400, Andrew Sullivan wrote:
> Because in the general case, you need the intermediate rows. The
> problem is that you'd have to write a special piece of code to catch
> the case where nobody else can see the row that you're about to
> expire, and that test isn't free. Therefore, you do it the same way
> any other row gets expired.

Just curious: is there a way to defeat MVCC? i.e., if you can lock the
database exclusively, there won't be any readers or writers?

Joe

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Andrew Sullivan 2007-04-13 17:01:08 Re: A long-running transaction
Previous Message Andrew Sullivan 2007-04-13 16:20:10 Re: A long-running transaction