Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Wed, 23 Apr 2008 08:51:32 +0100
- Message-id: <1208937092(dot)4259(dot)1276(dot)camel(at)ebony(dot)site>
On Tue, 2008-04-22 at 18:13 -0400, Alvaro Herrera wrote: > Simon Riggs wrote: > > > OK, so it can;t be copied to a longer lived memory context? > > CopySnapshot always copies snapshots to SnapshotContext, which is a > context that lives until transaction end. There's no mechanism for > copying a snapshot into another context, because I don't see the need. > > If you need that ability, please explain. No, I wish to prevent that, not enable it. Perhaps put the TransactionId on each snapshot and then an Assert can check it before its used. -- Simon Riggs 2ndQuadrant http://www.2ndQuadrant.com
- Follow-Ups:
- Re: Snapshot management, final
- From: Alvaro Herrera
- Re: Snapshot management, final
- References:
- Snapshot management, final
- From: Alvaro Herrera
- Re: Snapshot management, final
- From: Simon Riggs
- Re: Snapshot management, final
- From: Alvaro Herrera
- Re: Snapshot management, final
- From: Simon Riggs
- Re: Snapshot management, final
- From: Alvaro Herrera
- Snapshot management, final
- Prev by Date: Re: Snapshot management, final
- Next by Date: Re: Improve shutdown during online backup, take 3
- Previous by thread: Re: Snapshot management, final
- Next by thread: Re: Snapshot management, final
- Indexes: