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 1lZDWg-0003h0-G5 for pgsql-bugs@arkaria.postgresql.org; Wed, 21 Apr 2021 14:08: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 1lZDWf-0007Af-DU for pgsql-bugs@arkaria.postgresql.org; Wed, 21 Apr 2021 14:08:21 +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 1lZDWf-0007AY-4b for pgsql-bugs@lists.postgresql.org; Wed, 21 Apr 2021 14:08:21 +0000 Received: from mail-ed1-x52f.google.com ([2a00:1450:4864:20::52f]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lZDWc-0006mw-Pu for pgsql-bugs@lists.postgresql.org; Wed, 21 Apr 2021 14:08:20 +0000 Received: by mail-ed1-x52f.google.com with SMTP id z5so13021554edr.11 for ; Wed, 21 Apr 2021 07:08:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=x7dnQhf7qdU4/SWFuYj+fW1EbhB8Lzt3WNB/bM6d91c=; b=RD/x5Fu0pRQ4qIdKMczmS4K00MyvuZ6JabnjdESBStic9DTK8UswQjqWrpebuGH20W qLUQg7/Srz464QWLqRX2N7TEXWUqCEZLlCUGil+ELAqio6Wa/p1poqDxJaRnMmp0mlm6 CLbcPYqEZVLupSCRyWYa9vkpHWw8GsstH124QU08l+ojJp164ua3+IWgjJCLNoxXN7CV hAiS9ehrItvXyTI3ZPH9r74oVpM6bNRlq1qBIn97Knb9z/U2KkabrCjy4MC1gHteJXP8 xrcboJQzA8GSJvJC2r73Jo4MlBmGvbGEgYLzZaNAAIlJUXdGtQ/zbD7D1uCfvd+AU9g3 LHUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=x7dnQhf7qdU4/SWFuYj+fW1EbhB8Lzt3WNB/bM6d91c=; b=ChIzhuO0DZZ5h0AInzCWm8sFFmZRuw54XyetFQAlFZOyCXcJWY7i5caxeOkaTMZ2w2 NWO38XI3STogXOPWndOrwGFxFeQmDW0bJVAggElBis/oVCoY097Ei9W/nBRCZtW86cag NZ6yplz8U88pPp6zaD7FT+8zMH7h7PXjYJNqHrzmnOTah4mA34cZvwFcvj4x77qVORqX 9pV+val66f4jr3YPutxbSL+RE/bo/ZRbPNh4KTON92TfCATuwk1GTmOWxAi7YIg8khUe ysSoqvr99f0KU5g+F0vUPIIaZ0gftNNbh6HX7t1mBmZuGd5GceaNKsVi9y9kUJrx2Vj+ MEWQ== X-Gm-Message-State: AOAM530CSIcq8YyuS9smwXzMmbr47Fti0uKfQ2DWF/Jwd85ByXlXJXlR BShluGTDsVZKj1rdxCoIu6E= X-Google-Smtp-Source: ABdhPJz0HKODUT88zcHstiY/aA8581ndWXSxjdy/HgXH5K4MPZJdZx5xN1u/Cg1I4vvS/FjuZ39+GQ== X-Received: by 2002:aa7:cb97:: with SMTP id r23mr38395547edt.106.1619014097195; Wed, 21 Apr 2021 07:08:17 -0700 (PDT) Received: from [192.168.178.48] ([212.71.9.13]) by smtp.gmail.com with ESMTPSA id w6sm2564160eje.107.2021.04.21.07.08.16 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 21 Apr 2021 07:08:16 -0700 (PDT) Subject: Re: BUG #16976: server crash when deleting via a trigger on a foreign table To: Tom Lane , pgsql-bugs@lists.postgresql.org, PG Bug reporting form References: <16976-abe0cb88252bc02e@postgresql.org> <756273.1619012414@sss.pgh.pa.us> From: Herwig Goemans Message-ID: <45a2dc04-54a8-690d-a959-47e791a7f686@gmail.com> Date: Wed, 21 Apr 2021 16:08:16 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: <756273.1619012414@sss.pgh.pa.us> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: nl-BE List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, I was in the process of reproducing the problem and following the guidelines to produce the stack trace... but now it works. I asked my colleagues if they changed anything and will let you know. Thanks for the quick response, and I will keep you posted if I have any news. Kind regards, Herwig On 21/04/2021 15:40, Tom Lane wrote: >> I have experienced a server crash when deleting from a table that ahs a >> before trigger on it. The before trigger calls a function that deletes from >> a foreign (informix) table. > Hm, can you get a stack trace from that? > > https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend > > It seems fairly likely that the bug is in whatever FDW you're using > rather than in core Postgres. A stack trace would help to > confirm or refute that. > > regards, tom lane