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

[WIP] Keeping track of snapshots

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Pg Patches <pgsql-patches(at)postgresql(dot)org>
Subject: [WIP] Keeping track of snapshots
Date: 2008-03-28 14:06:06
Message-ID: 20080328140606.GL7464@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-patches
This is the patch I am currently playing with, to keep track of the
live snapshots within a transaction.

There are some obvious bugs left, and it open certain questions.  The
most obvious bug is that it is not tracking SerializableSnapshot in a
serializable transaction.

The main question I currently have is how to deal with ActiveSnapshot.
Currently, on most places it is just being registered just like any
snapshot, and then unregistered.  For the most part this works fine, but
I wonder if it's not just a bug waiting to happen -- since it is a
global variable and other places in the code feel free to assign to it,
it is possible that some code sets it, then calls some other code that
sets it to a different snapshot and then return -- on exit, the first
setter would try to unregister a snapshot that it didn't register.

So the question is, should we deal with ActiveSnapshot in some different
way?  For example snapmgr could know explicitely about it; keeping a
stack perhaps, and have callers call a routine in snapmgr "I need this
snap to be ActiveSnapshot" (push), and later "I no longer need
ActiveSnapshot" (pop).  On error, we can just forget about the part of
the stack that corresponds to the current subxact.  This would allow us
to remove some PG_TRY blocks.

The other question is about CommitTransactionCommand.  Currently my
EOXact routine barfs for every snapshot not unregistered on main
transaction commit -- a leak.  I see this as a good thing, however it
forced me to be more meticulous about not having ActiveSnapshot be set
in commands that have multiple transactions like VACUUM, multitable
CLUSTER and CREATE INDEX CONCURRENTLY.

(Hmm, maybe this last point is also saying that we should be dealing
with ActiveSnapshot explicitely on snapmgr.)


And finally, the last question is about some callers like COPY or
EXPLAIN that get a snapshot (ActiveSnapshot or a different one), then
modify Snapshot->curcid.  I'm not sure this is a problem, really, but
just to be careful I made them create a copy and register the copy.
The problem I have with it is that the snapshots are allocated only once
when they are registered -- if somebody registers the same snapshot in
the future, we will only increment the reference count and return the
pointer to the previously stored snapshot.  So if COPY reuses a snapshot
that has been previously stored, it would mangle the copy and the other
user could get an invalid view of the database.  I'm not sure this is
really a problem, because how could COPY get the same snapshot as
anybody else?  Still, it gives me a bad feeling.


(Hmm ... it just occured to me that perhaps it would be better to
improve the interaction between GetSnapshotData and RegisterSnapshot, to
avoid some palloc traffic.)

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

Attachment: snapshot-4.patch
Description: text/x-diff (42.8 KB)

Responses

pgsql-patches by date

Next:From: Gregory StarkDate: 2008-03-28 14:58:02
Subject: Re: [WIP] Keeping track of snapshots
Previous:From: Simon RiggsDate: 2008-03-28 13:14:38
Subject: Re: [PATCHES] Incomplete docs for restore_command for hotstandby

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