Re: Don't try fetching future segment of a TLI.

From: Grigory Smolkin <g(dot)smolkin(at)postgrespro(dot)ru>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Don't try fetching future segment of a TLI.
Date: 2020-04-07 09:36:18
Message-ID: c3f1c0f6-5e57-9b47-7dff-a21e760920b8@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

I`ve bumped into this issue recently:
https://www.postgresql.org/message-id/dd6690b0-ec03-6b3c-6fac-c963f91f87a7%40postgrespro.ru

On 4/6/20 8:43 PM, Fujii Masao wrote:

> The patch looks good to me. Attached is the updated version of the patch.
> I updated only comments.
>
> Barring any objection, I will commit this patch.

I`ve been running tests on your patch. So far so good.

On Tue, Apr 07, 2020 at 12:15:00PM +0900, Fujii Masao wrote:

> I understood the situation and am fine to back-patch that. But I'm not sure
> if it's fair to do that. Maybe we need to hear more opinions about this?
> OTOH, feature freeze for v13 is today, so what about committing the patch
> in v13 at first, and then doing the back-patch after hearing opinions and
> receiving many +1?

+1 to back-patching it.

--
Grigory Smolkin
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David Steele 2020-04-07 11:21:58 Re: Don't try fetching future segment of a TLI.
Previous Message 曾文旌 2020-04-07 09:30:03 [bug] Wrong bool value parameter

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2020-04-07 09:51:32 Re: pgsql: Generate backup manifests for base backups, and validate them.
Previous Message 曾文旌 2020-04-07 09:30:03 [bug] Wrong bool value parameter