Skip site navigation (1) Skip section navigation (2)

Re: Snapshot management, final

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Pg Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Snapshot management, final
Date: 2008-04-22 21:58:38
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
On Tue, 2008-04-22 at 17:50 -0400, Alvaro Herrera wrote:
> Simon Riggs wrote:
> > On Tue, 2008-04-22 at 15:49 -0400, Alvaro Herrera wrote:
> > 
> > > - Three CopySnapshot call sites remain outside snapmgr.c: DoCopy() on
> > > copy.c, ExplainOnePlan() on explain.c and _SPI_execute_plan() on spi.c.
> > > They are there because they grab the current ActiveSnapshot, modify it,
> > > and then use the resulting snapshot.  There is no corresponding
> > > FreeSnapshot, because it's not needed.
> > 
> > Not needed? How can we be certain that the modified snapshot does not
> > outlive its original source?
> It's not CopySnapshot that's not needed, but FreeSnapshot.  The point
> here is that the snapshot will be freed automatically as soon as it is
> PopActiveSnapshot'd out of existance.  CopySnapshot creates a new,
> separate copy of the passed snapshot, and each of them will be freed
> (separately) as soon as their refcounts reach zero.

OK, so it can;t be copied to a longer lived memory context?

  Simon Riggs

In response to


pgsql-patches by date

Next:From: Alvaro HerreraDate: 2008-04-22 22:13:00
Subject: Re: Snapshot management, final
Previous:From: Alvaro HerreraDate: 2008-04-22 21:50:56
Subject: Re: Snapshot management, final

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group