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

From David Steele
Subject Re: Don't try fetching future segment of a TLI.
Date
Msg-id 762ffb60-df9c-0efc-2714-9859219157e3@pgmasters.net
Whole thread Raw
In response to Re: Don't try fetching future segment of a TLI.  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Responses Re: Don't try fetching future segment of a TLI.  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Re: Don't try fetching future segment of a TLI.  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List pgsql-hackers
On 4/6/20 1:43 PM, Fujii Masao wrote:
> 
> 
> 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.

The patch looks good to me.

>> 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.

Not a bug, perhaps, but I think we do consider back-patching performance 
problems. The rise in S3 usage has just exposed how poorly this 
performed code in high-latency environments.

Regards,
-- 
-David
david@pgmasters.net



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] Restricting maximum keep segments by repslots
Next
From: Tom Lane
Date:
Subject: Re: DROP OWNED CASCADE vs Temp tables