Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lkRXT-0003yY-Sf for pgsql-hackers@arkaria.postgresql.org; Sat, 22 May 2021 13:19:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lkRWw-0005cc-B0 for pgsql-hackers@arkaria.postgresql.org; Sat, 22 May 2021 13:19:02 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lkRWw-0005az-3I for pgsql-hackers@lists.postgresql.org; Sat, 22 May 2021 13:19:02 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lkRWt-0007ki-Vc for pgsql-hackers@lists.postgresql.org; Sat, 22 May 2021 13:19:00 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 14MDIvUG228807; Sat, 22 May 2021 09:18:57 -0400 From: Tom Lane To: Amit Langote cc: Michael Paquier , Amit Kapila , PostgreSQL Hackers Subject: Re: Subscription tests fail under CLOBBER_CACHE_ALWAYS In-reply-to: References: <3382681.1621381328@sss.pgh.pa.us> <3392911.1621395985@sss.pgh.pa.us> <3508426.1621455835@sss.pgh.pa.us> <162691.1621630908@sss.pgh.pa.us> Comments: In-reply-to Amit Langote message dated "Sat, 22 May 2021 12:06:33 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <228805.1621689537.1@sss.pgh.pa.us> Date: Sat, 22 May 2021 09:18:57 -0400 Message-ID: <228806.1621689537@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Amit Langote 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? But I'm sort of inclined to back-patch to v11 as I did with 84f5c2908, mainly to keep the worker.c code looking more alike in those branches. regards, tom lane