From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
---|---|
To: | Pavel Suderevsky <psuderevsky(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net> |
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 17:43:02 |
Message-ID: | 792ea085-95c4-bca0-ae82-47fdc80e146d@oss.nttdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs 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 | Content-Type | Size |
---|---|---|
v2-0001-Don-t-try-fetching-out-of-timeline-segments.patch | text/plain | 1.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | David Steele | 2020-04-06 19:04:07 | Re: Don't try fetching future segment of a TLI. |
Previous Message | PG Bug reporting form | 2020-04-06 15:00:00 | BUG #16346: pg_upgrade fails on a trigger with a comment |
From | Date | Subject | |
---|---|---|---|
Next Message | Alexey Kondratov | 2020-04-06 17:43:46 | Re: Allow CLUSTER, VACUUM FULL and REINDEX to change tablespace on the fly |
Previous Message | Tom Lane | 2020-04-06 17:41:06 | Re: d25ea01275 and partitionwise join |