pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: David Steele <david@pgmasters.net>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: psuderevsky@gmail.com
Cc: pgsql-hackers@lists.postgresql.org
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Don't try fetching future segment of a TLI.
Date: Wed, 8 Apr 2020 01:49:27 +0900
Message-ID: <21d2590f-2739-9f45-748f-7a68d667d7cd@oss.nttdata.com> (raw)
In-Reply-To: <4a461c7b-b90a-6644-64a6-80eac69c27bc@pgmasters.net>
References: <792ea085-95c4-bca0-ae82-47fdc80e146d@oss.nttdata.com>
	<762ffb60-df9c-0efc-2714-9859219157e3@pgmasters.net>
	<3e0713d2-56d2-9883-4213-d5ba7f0dcabf@oss.nttdata.com>
	<20200407.164801.1830442317313243264.horikyota.ntt@gmail.com>
	<4a461c7b-b90a-6644-64a6-80eac69c27bc@pgmasters.net>



On 2020/04/07 20:21, David Steele wrote:
> 
> On 4/7/20 3:48 AM, Kyotaro Horiguchi wrote:
>> At Tue, 7 Apr 2020 12:15:00 +0900, Fujii Masao <masao.fujii@oss.nttdata.com> wrote in
>>>>> 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.
>>>
>>> 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 for commit only v13 today, then back-patch if people wants and/or
>> accepts.
> 
> Definitely +1 for a commit today to v13. I certainly was not trying to hold that up
Pushed the patch to v13, at first!

Regards,

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





view thread (13+ messages)

Message-ID: <21d2590f-2739-9f45-748f-7a68d667d7cd@oss.nttdata.com>
Permalink:  ../21d2590f-2739-9f45-748f-7a68d667d7cd@oss.nttdata.com/
Also on:    postgresql.org/message-id/21d2590f-2739-9f45-748f-7a68d667d7cd@oss.nttdata.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: masao.fujii@oss.nttdata.com, david@pgmasters.net, horikyota.ntt@gmail.com, psuderevsky@gmail.com, pgsql-hackers@lists.postgresql.org, pgsql-bugs@lists.postgresql.org
  Subject: Re: Don't try fetching future segment of a TLI.
  In-Reply-To: <21d2590f-2739-9f45-748f-7a68d667d7cd@oss.nttdata.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox