From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | KONDO Mitsumasa <kondo(dot)mitsumasa(at)lab(dot)ntt(dot)co(dot)jp> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Release note fix for timeline item |
Date: | 2013-10-08 14:26:26 |
Message-ID: | 20131008142626.GJ22450@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Tue, Oct 8, 2013 at 01:25:30PM +0900, KONDO Mitsumasa wrote:
> (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 creating 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>
First, I want to apologize for not completing the release notes earlier
so that others could review them. I started working on the release
notes on Friday, but my unfamiliarity with the process and fear of
making a mistake caused many delays. I have improved the documentation
on the process which will hopefully help next time.
Second, I have read the thread beind this patch:
You are right that there is alot of details skipped in the release note
text. I have developed the attached patch which I think does a better
job. Is it OK?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
Attachment | Content-Type | Size |
---|---|---|
recovery.diff | text/x-diff | 736 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2013-10-08 14:29:49 | pgsql: Additional instructions on minor release note creation. |
Previous Message | Bruce Momjian | 2013-10-08 13:48:35 | pgsql: Update instructions on creating minor release notes. |
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2013-10-08 14:28:24 | Re: Re: custom hash-based COUNT(DISTINCT) aggregate - unexpectedly high memory consumption |
Previous Message | Andrew Dunstan | 2013-10-08 14:04:28 | Re: Bugfix and new feature for PGXS |