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

Re: BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Randy Isbell <jisbell(at)cisco(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION
Date: 2009-01-15 23:54:03
Message-ID: 200901152354.n0FNs3J18213@momjian.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-docspgsql-hackers
Heikki has updated the documentation to mention the meaning of this
field.  Thanks for the report.

---------------------------------------------------------------------------

Fujii Masao wrote:
> On Fri, Dec 5, 2008 at 11:41 PM, Randy Isbell <jisbell(at)cisco(dot)com> wrote:
> >
> > The following bug has been logged online:
> >
> > Bug reference:      4566
> > Logged by:          Randy Isbell
> > Email address:      jisbell(at)cisco(dot)com
> > PostgreSQL version: 8.3.4
> > Operating system:   FreeBSD 6.2
> > Description:        pg_stop_backup() reports incorrect STOP WAL LOCATION
> > Details:
> >
> > An inconsistency exists between the segment name reported by
> > pg_stop_backup() and the actual WAL file name.
> >
> >
> > SELECT pg_start_backup('filename');
> >         pg_start_backup
> >        -----------------
> >         10/FE1E2BAC
> >        (1 row)
> >
> > Later:
> > SELECT pg_stop_backup();
> >         pg_stop_backup
> >        ----------------
> >         10/FF000000
> >        (1 row)
> >
> > The resulting *.backup file:
> >
> > START WAL LOCATION: 10/FE1E2BAC (file 0000000200000010000000FE)
> > STOP WAL LOCATION: 10/FF000000 (file 0000000200000010000000FF)
> > CHECKPOINT LOCATION: 10/FE1E2BAC
> > START TIME: 2008-11-09 01:15:06 CST
> > LABEL: /bck/db/sn200811090115.tar.gz
> > STOP TIME: 2008-11-09 01:15:48 CST
> >
> > In my 8.3.4 instance, WAL file naming occurs as:
> >
> > ...
> > 0000000100000003000000FD
> > 0000000100000003000000FE
> > 000000010000000400000000
> > 000000010000000400000001
> > ...
> >
> > WAL files never end in 'FF'.  This causes a problem when trying to collect
> > the ending WAL file for backup.
> 
> It's a bug of pg_stop_backup(), which has been talked before.
> http://archives.postgresql.org/pgsql-hackers/2008-12/msg00108.php
> 
> Attached is a patch against HEAD. I think that we should
> also backport.
> 
> Regards,
> 
> -- 
> Fujii Masao
> NIPPON TELEGRAPH AND TELEPHONE CORPORATION
> NTT Open Source Software Center

[ Attachment, skipping... ]

> 
> -- 
> Sent via pgsql-bugs mailing list (pgsql-bugs(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs

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

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

In response to

pgsql-docs by date

Next:From: Fujii MasaoDate: 2009-01-16 02:18:49
Subject: Re: BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION
Previous:From: Simon RiggsDate: 2009-01-15 17:51:35
Subject: Re: BUG #4566: pg_stop_backup() reports incorrect STOP WALLOCATION

pgsql-hackers by date

Next:From: Justin PasherDate: 2009-01-16 00:05:39
Subject: Re: Autovacuum daemon terminated by signal 11
Previous:From: Tom LaneDate: 2009-01-15 23:44:04
Subject: Re: Autovacuum daemon terminated by signal 11

pgsql-bugs by date

Next:From: brianDate: 2009-01-16 00:41:46
Subject: BUG #4618: nolock changes first column name of query result set to 'nolock'
Previous:From: Marshall, SteveDate: 2009-01-15 22:33:11
Subject: pg_listener entries deleted under heavy NOTIFY load only on Windows

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