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 1q033d-00064v-F8 for pgsql-hackers@arkaria.postgresql.org; Fri, 19 May 2023 16:34:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q033c-0000NU-3s for pgsql-hackers@arkaria.postgresql.org; Fri, 19 May 2023 16:34:20 +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 1q033b-0000NL-Kw for pgsql-hackers@lists.postgresql.org; Fri, 19 May 2023 16:34:19 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by makus.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1q033Y-000hbf-51 for pgsql-hackers@postgresql.org; Fri, 19 May 2023 16:34:18 +0000 Received: from mail.postgrespro.ru (webmail.mstn.postgrespro.ru [192.168.2.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mail.postgrespro.ru (Postfix/587) with ESMTPSA id 48A09E20FD8; Fri, 19 May 2023 19:35:01 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1684514101; bh=yZFiYNIO1Fr8xrvgfDwoiT9V6Wy8K/xXZXMw4HPEvdY=; h=Date:From:To:Cc:Subject:In-Reply-To:References:User-Agent: Message-ID:From; b=YHW5M6PLg2nVIJz2KcDvsvL096nhKtXjx8AXTE4treVu03WM4IzhxX7zcvMoPoefD WXKpVPKztWcTSRFinutGBwJgeIcT55sxylHxThQFTC5YptJTz+d+DRuqqk4f9upT9B vhZrHK5xQh6MPg3RaUdP4qbHJa2O9UYNcyDSa7FsGFS8qvciY72ehRAvHRFNfLYW2T YMYjRVS43AI/RiyGwUZSyemdT735X0/C1i3ZiRp2z9au164GoN/UCdXeGNL4MVtt8X AXiRJsJjRHCDC7oT6cNdKW3vCFwWG0J9EruKTpw6c5uSIQz6KlgMgttgWG5eyC/gj+ i7Fy39Lo0kVYg== MIME-Version: 1.0 Date: Fri, 19 May 2023 19:34:13 +0300 From: Marina Polyakova To: Tom Lane Cc: Michael Paquier , pgsql-hackers@postgresql.org, Noah Misch , exclusion@gmail.com Subject: Re: Conflict between regression tests namespace & transactions due to recent changes In-Reply-To: <97962.1684508387@sss.pgh.pa.us> References: <80d0201636665d82185942e7112257b4@postgrespro.ru> <2165312.1684167368@sss.pgh.pa.us> <6524e1f13ab39669f3409543e4781269@postgrespro.ru> <97962.1684508387@sss.pgh.pa.us> User-Agent: Roundcube Webmail/1.4.11 Message-ID: <731b244af8bc4cffa47f18cb91e911ee@postgrespro.ru> X-Sender: m.polyakova@postgrespro.ru Organization: Postgres Professional Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2023-05-19 17:59, Tom Lane wrote: > Marina Polyakova writes: >> On 2023-05-19 09:03, Michael Paquier wrote: >>> FYI, the buildfarm is seeing some spurious failures as well: >>> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=schnauzer&dt=2023-05-1904%3A29%3A42 > >> Yes, it is the same error. Here's another one in version 13: >> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=schnauzer&dt=2023-05-18%2022:37:49 > > Right. I went ahead and pushed the fix in hopes of stabilizing things. > (I went with "trans_abc" as the new table name, for consistency with > some other nearby names.) > > regards, tom lane Thank you! I missed the same changes in version 11 :( -- Marina Polyakova Postgres Professional: http://www.postgrespro.com The Russian Postgres Company