From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Subscription tests fail under CLOBBER_CACHE_ALWAYS |
Date: | 2021-05-23 08:38:31 |
Message-ID: | YKoUh18SDF2eLRX7@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, May 23, 2021 at 02:05:59PM +0900, Amit Langote wrote:
> On Sun, May 23, 2021 at 10:28 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I wrote:
>> > ... wrong. Running v13 branch tip under CLOBBER_CACHE_ALWAYS provokes
>> > a core dump in 013_partition.pl, so 1375422c is not to blame. Now
>> > I'm wondering how far back there's a live issue.
>>
>> Oh, of course, it's directly the fault of the patch that added support
>> for partitioned target tables.
>
> Yeah, the problem seems to affect only partition child tables, so yeah
> this problem started with f1ac27bfda6.
Yep.
>> I concluded that a verbatim backpatch wasn't too suitable because
>> a04daa97a had changed a lot of the APIs here. So I left the APIs
>> for the xxx_internal() functions alone. Otherwise the patch
>> pretty much works as-is in v13.
Thanks for the backpatch of the partition tests via d18ee6f.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Dilip Kumar | 2021-05-23 08:49:18 | Re: Race condition in recovery? |
Previous Message | David Rowley | 2021-05-23 07:01:30 | RelOptInfo.all_partrels does not seem to do very much |