Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sFxfK-007mCK-Lh for pgsql-bugs@arkaria.postgresql.org; Sat, 08 Jun 2024 15:07:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sFxfJ-00Hagd-54 for pgsql-bugs@arkaria.postgresql.org; Sat, 08 Jun 2024 15:07:34 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sFxfI-00HagV-ST for pgsql-bugs@lists.postgresql.org; Sat, 08 Jun 2024 15:07:33 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sFxfC-000KGR-Ul for pgsql-bugs@lists.postgresql.org; Sat, 08 Jun 2024 15:07:32 +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 458F7NDC336834; Sat, 8 Jun 2024 11:07:23 -0400 From: Tom Lane To: Alexander Lakhin cc: Michael Paquier , a.kozhemyakin@postgrespro.ru, pgsql-bugs@lists.postgresql.org, Masahiko Sawada , johncnaylorls@gmail.com Subject: Re: BUG #18483: Segmentation fault in tests modules In-reply-to: <439c9310-1d71-f2c6-b213-a9a2ea732ba9@gmail.com> References: <18483-30bfff42de238000@postgresql.org> <219049.1717792376@sss.pgh.pa.us> <439c9310-1d71-f2c6-b213-a9a2ea732ba9@gmail.com> Comments: In-reply-to Alexander Lakhin message dated "Sat, 08 Jun 2024 08:00:00 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <336832.1717859243.1@sss.pgh.pa.us> Date: Sat, 08 Jun 2024 11:07:23 -0400 Message-ID: <336833.1717859243@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Alexander Lakhin writes: > May I ask you about the project policy regarding such test modules > failures? > Do you think all of these should be fixed or it's ok to have some > server-crashing modules in the tree? I don't think there's a one-size-fits-all policy for them. Since we don't intend these modules to be installed, they don't really need to work in any cases beyond the ones exercised in the tests. Still, if it's easy to stop a misbehavior then we probably should. The test_predtest problem was just a missing check-for-null so I definitely regard that as worth fixing. These other ones would have to be investigated enough to figure out the size of the fix before I'd venture an opinion. regards, tom lane