| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Pavel Suderevsky <psuderevsky(at)gmail(dot)com> |
| Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Don't try fetching future segment of a TLI. |
| Date: | 2020-04-06 19:04:07 |
| Message-ID: | 762ffb60-df9c-0efc-2714-9859219157e3@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs 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(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-04-06 19:08:49 | Re: DROP OWNED CASCADE vs Temp tables |
| Previous Message | Fujii Masao | 2020-04-06 17:43:02 | Re: Don't try fetching future segment of a TLI. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-04-06 19:08:49 | Re: DROP OWNED CASCADE vs Temp tables |
| Previous Message | Alvaro Herrera | 2020-04-06 18:58:39 | Re: [HACKERS] Restricting maximum keep segments by repslots |