Re: Improvement of procArray.xmin for VACUUM

From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Bruce Momjian" <bruce(at)momjian(dot)us>, "PostgreSQL-patches" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Improvement of procArray.xmin for VACUUM
Date: 2007-03-26 19:27:11
Message-ID: 1174937231.6069.428.camel@silverbirch.site
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

On Fri, 2007-03-23 at 17:35 -0400, Tom Lane wrote:
> To make intra-transaction advancing of xmin possible, we'd need to
> explicitly track all of the backend's live snapshots, probably by
> introducing a "snapshot cache" manager that gives out tracked
> refcounts
> as we do for some other structures like catcache entries. This might
> have some other advantages (I think most of the current CopySnapshot
> operations could be replaced by refcount increments)

Seems like we should do this for many reasons, whether or not this is
one of them. I seem to have butted heads and lost more than once with
not being able to tell which Snapshots exist.

--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Simon Riggs 2007-03-26 19:37:16 Re: Improvement of procArray.xmin for VACUUM
Previous Message Tom Lane 2007-03-26 17:01:09 Re: [pgsql-patches] [HACKERS] less privileged pl install