Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:

> On Fri, Dec 5, 2008 at 11:41 PM, Randy Isbell <jisbell(at)cisco(dot)com> wrote:
> > An inconsistency exists between the segment name reported by
> > pg_stop_backup() and the actual WAL file name.
> >
> > START WAL LOCATION: 10/FE1E2BAC (file 0000000200000010000000FE)
> > STOP WAL LOCATION: 10/FF000000 (file 0000000200000010000000FF)

> But it was rejected because its change might break the existing app.

It might break existing applications if it returns "FE" instead of "FF",
but never-used filename surprises users. (IMO, the existing apps probably
crash if "FF" returned, i.e, 1/256 of the time.)

Should it return the *next* reasonable log filename instead of "FF"?
For example, 000000020000002000000000 for the above case.

Regards,
---
Takahiro Itagaki
NTT Open Source Software Center

In response to

• Re: [BUGS] BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION at 2010-02-04 07:28:03 from Fujii Masao

Responses

• Re: Re: [BUGS] BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION at 2010-02-05 00:54:14 from Fujii Masao
• Re: Re: [BUGS] BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION at 2010-02-16 05:19:15 from Fujii Masao

pgsql-docs by date

Next:	From: Fujii Masao	Date: 2010-02-05 00:54:14
	Subject: Re: Re: [BUGS] BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION
Previous:	From: Bruce Momjian	Date: 2010-02-04 16:04:58
	Subject: Re: Administration book proofreading

pgsql-hackers by date

Next:	From: Fujii Masao	Date: 2010-02-05 00:54:14
	Subject: Re: Re: [BUGS] BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION
Previous:	From: Tom Lane	Date: 2010-02-04 23:53:46
	Subject: pg_class has no toast table?

pgsql-bugs by date

Next:	From: Fujii Masao	Date: 2010-02-05 00:54:14
	Subject: Re: Re: [BUGS] BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION
Previous:	From: Mark Kirkwood	Date: 2010-02-04 23:21:12
	Subject: Re: BUG #5312: I NEED HELP