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 1pztmC-0004jn-Qe for pgsql-hackers@arkaria.postgresql.org; Fri, 19 May 2023 06:39:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pztmB-00088v-Mb for pgsql-hackers@arkaria.postgresql.org; Fri, 19 May 2023 06:39:43 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pztmB-00088m-8Y for pgsql-hackers@lists.postgresql.org; Fri, 19 May 2023 06:39:43 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by magus.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1pztm7-000fvf-Kn for pgsql-hackers@postgresql.org; Fri, 19 May 2023 06:39:42 +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 CAC2BE20FF1; Fri, 19 May 2023 09:40:25 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1684478425; bh=EsyLBpCku+YtuAAwPcvE9dE53YBjLf7tFF8eEYrpe8c=; h=Date:From:To:Cc:Subject:In-Reply-To:References:User-Agent: Message-ID:From; b=BmjNckaAt+aeiJeftqwDO2Y2+ITis4nwYxdgBynpsuR52nV+E7b1GkLDeOHQ9Tj7C KLahGIKBmCI7sS5ZXx0sVyAUiBlBv5eP6SJBEv7TIRBiWk4Gu5AxXdUSVGJht7f77+ 6DHd9rBHY9lAu4gD7O00Ra2Jtxj///x9PpCdeLZBoQzHrMcd7sM/Xg39eLEmGgDYqc waPybFgGIDfZBy652gA+G3dgqH6I/g8NTQXDTIPboFBQErEehydTPNXPKx+r6RUEjs nzW7LRUhLYcYfWyiN2ha5TMsC7MjAeNrmwg3Op/UN3G5JRE8Idn/RFfBnbWpNED6IE JL7e53zozCK3A== MIME-Version: 1.0 Date: Fri, 19 May 2023 09:39:39 +0300 From: Marina Polyakova To: Michael Paquier Cc: Tom Lane , pgsql-hackers@postgresql.org, Noah Misch , exclusion@gmail.com Subject: Re: Conflict between regression tests namespace & transactions due to recent changes In-Reply-To: References: <80d0201636665d82185942e7112257b4@postgrespro.ru> <2165312.1684167368@sss.pgh.pa.us> User-Agent: Roundcube Webmail/1.4.11 Message-ID: <6524e1f13ab39669f3409543e4781269@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 09:03, Michael Paquier wrote: > On Wed, May 17, 2023 at 02:39:10PM +0900, Michael Paquier wrote: >> On Tue, May 16, 2023 at 11:02:45AM +0300, Marina Polyakova wrote: >>> It confuses me a little that different methods are used for the same >>> purpose. But the namespace test checks schemas. So see >>> diff_abc_to_txn_table.patch which replaces abc with txn_table in the >>> transaction test. >> >> Looks OK seen from here. Thanks! > > FYI, the buildfarm is seeing some spurious failures as well: > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=schnauzer&dt=2023-05-19 > 04%3A29%3A42 > -- > Michael 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 -- Marina Polyakova Postgres Professional: http://www.postgrespro.com The Russian Postgres Company