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 1kED9M-0001xj-EB for pgsql-bugs@arkaria.postgresql.org; Fri, 04 Sep 2020 14:57:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kED9L-0006rv-CD for pgsql-bugs@arkaria.postgresql.org; Fri, 04 Sep 2020 14:57:11 +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 1kED9K-0006r1-S6 for pgsql-bugs@lists.postgresql.org; Fri, 04 Sep 2020 14:57:11 +0000 Received: from mail.dalibo.com ([212.85.157.172]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kED9D-0004Nv-KB for pgsql-bugs@lists.postgresql.org; Fri, 04 Sep 2020 14:57:09 +0000 Received: from firost (larco.ioguix.net [82.66.0.6]) by mail.dalibo.com (Postfix) with ESMTPSA id 80BCA2049C; Fri, 4 Sep 2020 16:56:59 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dalibo.com; s=a; t=1599231419; bh=zx2L7irAqv+ygh3r6lwuPGRrk5S7PJCEUKFkh1WFWTg=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=Yf3YBV0LEQtKIKLKI1y5flY4j9cXHv5X3VwrO5R2d8gGfIprJFE4jhilXUID/BAJW ZyvbKT2IrIFm2T3yMwx6m8NaV8INp42oGNe543xUF7b8e52EI0DKmhckKSTn5GNjaj hEH6rBhs1aJ8UhUAljRQns5vlqjoTNs7ETqwp+aY= Date: Fri, 4 Sep 2020 16:56:58 +0200 From: Jehan-Guillaume de Rorthais To: Alvaro Herrera Cc: Michael Paquier , pgsql-bugs@lists.postgresql.org Subject: Re: [BUG v13] Crash with event trigger in extension Message-ID: <20200904165658.3c57fa4a@firost> In-Reply-To: <20200904132715.GA5969@alvherre.pgsql> References: <20200904113728.2d4a44bb@firost> <20200904132715.GA5969@alvherre.pgsql> Organization: Dalibo MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="MP_/eLuKpl=kY8XLAf7c4v.x5Vr" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --MP_/eLuKpl=kY8XLAf7c4v.x5Vr Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline On Fri, 4 Sep 2020 09:27:15 -0400 Alvaro Herrera wrote: > On 2020-Sep-04, Jehan-Guillaume de Rorthais wrote: > > > Indeed, it's much more simple and cheaper. However, the result is a bit > > confusing as it's not a wrong SQL result, but the backend that actually > > crash. The crash message itself appears in results/test_extensions.out, but > > no other tests are run. Neither from the same SQL file or from other ones. > > That Means the diff is quite large, but the error appears close from the > > top. > > Oh! If it crashes without the extension, then we don't *need* the > exension and surely we don't need the test to be in src/test/modules/; Oh wait. It's not what I meant. We *need* an extension to trigger the backend crash. > my inclination would be to put it somewhere in > src/test/regress/sql/event_triggers.sql, maybe at the bottom, with a > comment that references this thread. As the regression need an extension to be installed, it still makes sens to test from src/test/modules/test_extension where various extensions are installed to run the checks. Please find in attachment patch v3. --MP_/eLuKpl=kY8XLAf7c4v.x5Vr Content-Type: text/x-patch Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=v3-0001-Fix-crash-with-alter-table-event-triggers-in-extensi.patch