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

pgsql: Fix snapshot management, take two.

From: alvherre(at)postgresql(dot)org (Alvaro Herrera)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix snapshot management, take two.
Date: 2009-10-07 16:27:29
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committers
Log Message:
Fix snapshot management, take two.

Partially revert the previous patch I installed and replace it with a more
general fix: any time a snapshot is pushed as Active, we need to ensure that it
will not be modified in the future.  This means that if the same snapshot is
used as CurrentSnapshot, it needs to be copied separately.  This affects
serializable transactions only, because CurrentSnapshot has already been copied
by RegisterSnapshot and so PushActiveSnapshot does not think it needs another
copy.  However, CommandCounterIncrement would modify CurrentSnapshot, whereas
ActiveSnapshots must not have their command counters incremented.

I say "partially" because the regression test I added for the previous bug
has been kept.

(This restores 8.3 behavior, because before snapmgr.c existed, any snapshot set
as Active was copied.)

Per bug report from Stuart Bishop in 


Modified Files:
        portalcmds.c (r1.79.2.1 -> r1.79.2.2)
        snapmgr.c (r1.10.2.1 -> r1.10.2.2)
        snapmgr.h (r1.5.2.1 -> r1.5.2.2)
        triggers.out (r1.26 -> r1.26.2.1)
        triggers.sql (r1.15 -> r1.15.2.1)

pgsql-committers by date

Next:From: Alvaro HerreraDate: 2009-10-07 22:14:26
Subject: pgsql: Make it possibly to specify GUC params per user and per database.
Previous:From: Alvaro HerreraDate: 2009-10-07 16:27:18
Subject: pgsql: Fix snapshot management, take two.

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