Re: Don't try fetching future segment of a TLI. - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Don't try fetching future segment of a TLI.
Date
Msg-id 792ea085-95c4-bca0-ae82-47fdc80e146d@oss.nttdata.com
Whole thread Raw
In response to Re: Don't try fetching future segment of a TLI.  (Pavel Suderevsky <psuderevsky@gmail.com>)
Responses Re: Don't try fetching future segment of a TLI.  (David Steele <david@pgmasters.net>)
Re: Don't try fetching future segment of a TLI.  (David Steele <david@pgmasters.net>)
Re: Don't try fetching future segment of a TLI.  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Re: Don't try fetching future segment of a TLI.  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
List pgsql-hackers

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.

Barring any objection, I will commit this patch.

> Any chance it will be merged to one of the next minor releases?

This doesn't seem a bug, so I'm thinking to merge this to next *major*
version release, i.e., v13.

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: d25ea01275 and partitionwise join
Next
From: Alexey Kondratov
Date:
Subject: Re: Allow CLUSTER, VACUUM FULL and REINDEX to change tablespace onthe fly