Re: pgsql: docs: update release notes for 8.4.18, 9.0.14, 9.1.10, 9.2.5, 9

From: KONDO Mitsumasa <kondo(dot)mitsumasa(at)lab(dot)ntt(dot)co(dot)jp>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: docs: update release notes for 8.4.18, 9.0.14, 9.1.10, 9.2.5, 9
Date: 2013-10-08 04:25:30
Message-ID: 5253893A.8020606@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

(2013/10/08 10:35), Bruce Momjian wrote:
> docs: update release notes for 8.4.18, 9.0.14, 9.1.10, 9.2.5, 9.3.1
Thank you for createing good release note. I have one comment.

In 9.1 and 9.2 release note, Is "Improve WAL segment timeline handling during
recovery" means commit which is "Install recycled WAL segments with current
timeline ID during recovery"? This is not so simple problem fix.
This bug caused failing PITR which is finished archive recovery on the way. When
it occered, it seemed to finish archive recovery without problem.

I think it is comparatively big problem, so we should write it in release note.
Please fix it under following.

+ <listitem>
+ <para>
+ Fix WAL segment timeline handling during recovery (Mitsumasa
+ KONDO, Heikki Linnakangas)
+ </para>
+
+ <para>
+ When target timeline is up and executing restart point in archive recovery
+ mode, archive recovery is failed on the way, because failing recycle of +
WAL. When this problem occurred, it seemed to finish success of archive +
recovery without problem.
+ </para>
+ </listitem>

Regards,
--
Mitsumasa KONDO
NTT Open Source Software Center

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2013-10-08 06:52:08 Re: [COMMITTERS] pgsql: Add DISCARD SEQUENCES command.
Previous Message Peter Eisentraut 2013-10-08 03:19:40 pgsql: Stamp 9.1.10.

Browse pgsql-hackers by date

  From Date Subject
Next Message Claudio Freire 2013-10-08 05:11:25 Re: Re: custom hash-based COUNT(DISTINCT) aggregate - unexpectedly high memory consumption
Previous Message Atri Sharma 2013-10-08 04:23:37 Re: Re: custom hash-based COUNT(DISTINCT) aggregate - unexpectedly high memory consumption