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

Re: pgsql: pg_stop_backup was

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)postgresql(dot)org>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: pg_stop_backup was
Date: 2006-11-14 22:40:38
Message-ID: 200611142240.kAEMec002035@momjian.us (view raw or flat)
Thread:
Lists: pgsql-committers
Simon Riggs wrote:
> On Thu, 2006-06-22 at 17:43 -0300, Tom Lane wrote:
> > Log Message:
> > -----------
> > pg_stop_backup was calling XLogArchiveNotify() twice for the newly created
> > backup history file.  Bug introduced by the 8.1 change to make pg_stop_backup
> > delete older history files.  Per report from Masao Fujii.
> > 
> > Tags:
> > ----
> > REL8_1_STABLE
> > 
> > Modified Files:
> > --------------
> >     pgsql/src/backend/access/transam:
> >         xlog.c (r1.222.2.3 -> r1.222.2.4)
> >         (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c.diff?r1=1.222.2.3&r2=1.222.2.4)
> 
> 
> This doesn't seem to be mentioned in the 8.1.5 release notes, so people
> would not be aware they should upgrade to fix this.

We don't mention every fix for every minor release.  People should
upgrade anyway, as we state in the FAQ.  Is there a reason this item was
significant?

-- 
  Bruce Momjian   bruce(at)momjian(dot)us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

Responses

pgsql-committers by date

Next:From: Bruce MomjianDate: 2006-11-15 01:09:09
Subject: pgsql: Improve broadcast wording for failover/clustering documentation.
Previous:From: Simon RiggsDate: 2006-11-14 22:28:36
Subject: Re: pgsql: pg_stop_backup was callingXLogArchiveNotify() twice for the

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