From: David Steele <david@pgmasters.net>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
To: masao.fujii@oss.nttdata.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: Tue, 7 Apr 2020 07:21:58 -0400
Message-ID: <4a461c7b-b90a-6644-64a6-80eac69c27bc@pgmasters.net> (raw)
In-Reply-To: <20200407.164801.1830442317313243264.horikyota.ntt@gmail.com>
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>
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.
--
-David
david@pgmasters.net
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: david@pgmasters.net, horikyota.ntt@gmail.com, masao.fujii@oss.nttdata.com, psuderevsky@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Don't try fetching future segment of a TLI.
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>
* 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