Re: Don't try fetching future segment of a TLI.
Kyotaro Horiguchi <horikyota.ntt@gmail.com>
From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
To: masao.fujii@oss.nttdata.com
Cc: psuderevsky@gmail.com, david@pgmasters.net,
pgsql-hackers@lists.postgresql.org, pgsql-bugs@lists.postgresql.org
Date: 2020-04-07T01:29:09Z
Lists: pgsql-bugs, pgsql-hackers
Thank you for picking this up. At Tue, 7 Apr 2020 02:43:02 +0900, Fujii Masao <masao.fujii@oss.nttdata.com> wrote in > On 2020/03/19 22:22, Pavel Suderevsky wrote: > > Hi, > > I've tested patch provided by Kyotaro and do confirm it fixes the > > issue. > > The patch looks good to me. Attached is the updated version of the > patch. > I updated only comments. + * The logfile segment that doesn't belong to the timeline is + * older or newer than the segment that the timeline started or + * eneded at, respectively. It's sufficient to check only the s/eneded/ended/ ? regards. -- Kyotaro Horiguchi NTT Open Source Software Center
Commits
-
Prevent archive recovery from scanning non-existent WAL files.
- e3f5b148ed32 9.5.22 landed
- 70b5979742f8 9.6.18 landed
- 660f1fc40d7a 10.13 landed
- dcd1569fb05d 11.8 landed
- 683e0ef5530f 12.3 landed
- 4bd0ad9e44be 13.0 landed