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

pgsql: Initialize shared memory copy of ckptXidEpoch correctly whennot

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Initialize shared memory copy of ckptXidEpoch correctly whennot
Date: 2012-06-29 16:33:34
Message-ID: E1Ske8U-0003zw-Nm@gemulon.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Initialize shared memory copy of ckptXidEpoch correctly when not in recovery.

This bug was introduced by commit 20d98ab6e4110087d1816cd105a40fcc8ce0a307,
so backpatch this to 9.0-9.2 like that one.

This fixes bug #6710, reported by Tarvi Pillessaar

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/7a5c9ca93ad7d9b84f612d6157bf8990c7041d3c

Modified Files
--------------
src/backend/access/transam/xlog.c |    7 +++----
1 files changed, 3 insertions(+), 4 deletions(-)

pgsql-committers by date

Next:From: Alvaro HerreraDate: 2012-06-29 16:59:29
Subject: Re: pgsql: pg_dump: Fix verbosity level in LO progress messages
Previous:From: Alvaro HerreraDate: 2012-06-29 16:12:07
Subject: pgsql: pg_dump: Fix verbosity level in LO progress messages

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