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

pgsql: Fix overly strict assertion inSummarizeOldestCommittedSxact().

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix overly strict assertion inSummarizeOldestCommittedSxact().
Date: 2011-03-08 19:06:48
Message-ID: E1Px2F6-0007fk-ON@gemulon.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Fix overly strict assertion in SummarizeOldestCommittedSxact(). There's a
race condition where SummarizeOldestCommittedSxact() is called even though
another backend already cleared out all finished sxact entries. That's OK,
RegisterSerializableTransactionInt() can just retry getting a news xact
slot from the available-list when that happens.

Reported by YAMAMOTO Takashi, bug #5918.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/46c333a9638b329a3c8076d978f27c5b05c0d5f0

Modified Files
--------------
src/backend/storage/lmgr/predicate.c |   14 ++++++++++----
1 files changed, 10 insertions(+), 4 deletions(-)

pgsql-committers by date

Next:From: Peter EisentrautDate: 2011-03-08 20:11:00
Subject: pgsql: Ignore files built by coverage builds
Previous:From: Heikki LinnakangasDate: 2011-03-08 19:00:22
Subject: pgsql: Don't throw a warning if vacuum sees PD_ALL_VISIBLE flag seton

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