From: Tom Lane <tgl@sss.pgh.pa.us>
To: Amit Langote <amitlangote09@gmail.com>
cc: Michael Paquier <michael@paquier.xyz>,
        Amit Kapila <amit.kapila16@gmail.com>,
        PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Subscription tests fail under CLOBBER_CACHE_ALWAYS
In-reply-to: <228806.1621689537@sss.pgh.pa.us>
References: <3382681.1621381328@sss.pgh.pa.us> <YKSAFhtltIr9GUEi@paquier.xyz>
 <3392911.1621395985@sss.pgh.pa.us> <YKSSj5yQOg1twolW@paquier.xyz>
 <CAA4eK1L_vVJyy_hAdNCzsFXYcdZ=UO_9UrYX=+GZeb4CBeLJ1Q@mail.gmail.com>
 <YKSciAJEPQ7wmNDt@paquier.xyz>
 <CA+HiwqEW7kVF+VKdHT7TnzQGab9-dP9tLyedVvs5nQ7yJ_BP6g@mail.gmail.com>
 <3508426.1621455835@sss.pgh.pa.us>
 <CA+HiwqF6HXDTnkcb07HV+ErzcYpAL_0_MwviNwGi+VkzbYdkEQ@mail.gmail.com>
 <162691.1621630908@sss.pgh.pa.us>
 <CA+HiwqFnbV7W7j4S3s8pKaCe58stWMFzTsvUgC7SP2WKC-aSRQ@mail.gmail.com>
 <228806.1621689537@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Sat, 22 May 2021 09:18:57 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <264713.1621697563.1@sss.pgh.pa.us>
Date: Sat, 22 May 2021 11:32:43 -0400
Message-ID: <264714.1621697563@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/264714.1621697563%40sss.pgh.pa.us>
Precedence: bulk

I wrote:
> Amit Langote <amitlangote09@gmail.com> writes:
>> BTW, I think we'd need to cherry-pick f3b141c4825 (or maybe parts of
>> it) into v13 branch for back-patching this.

> I already did a fair amount of that yesterday, cf 84f5c2908 et al.
> But that does raise the question of how far we need to back-patch this.
> I gather that the whole issue might've started with 1375422c, so maybe
> we don't really need a back-patch at all?

... 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.

			regards, tom lane