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 1lZa2V-000504-3S for pgsql-bugs@arkaria.postgresql.org; Thu, 22 Apr 2021 14:10:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lZa2U-0005Lj-1f for pgsql-bugs@arkaria.postgresql.org; Thu, 22 Apr 2021 14:10:42 +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 1lZa2T-0005Lc-PI for pgsql-bugs@lists.postgresql.org; Thu, 22 Apr 2021 14:10:41 +0000 Received: from mail-ej1-x635.google.com ([2a00:1450:4864:20::635]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lZa2R-00024V-4x for pgsql-bugs@lists.postgresql.org; Thu, 22 Apr 2021 14:10:41 +0000 Received: by mail-ej1-x635.google.com with SMTP id l4so68962555ejc.10 for ; Thu, 22 Apr 2021 07:10:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=uSqjEsJ4BND+K72cCQBvAdOo6MhawjDQr2xUKXVXj50=; b=KMpAIPDEL8wVupr3FafA32BzrB5z8O4e6MopOvA+gyAM8mupWLbFkDUwhgocEcGQR5 lPHdQFUBbU5v8cbZJgaatWP02HOB5kYT9aK0f21wBiGB++QPjFYTo1S8ruMB8uq1pLcN 7GXzIteHJ4T6tKAs8NxSCHJs0Qf1JC9BLa4uv1RcqfbxFzF9w70P36/lWIOHRX3eNS19 sfTS5fWz8utv3scOeuUVEPseAmdNp+C67QRcutR73BPMc6uxrMYHQrE9LFh11UEJpcg2 6Wnc/M1ylmnIwka6oxvxs6341KPuQpR/kqxpx7z9+k7Sv34f9IS/7CY416lcTSJPAI13 2QTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=uSqjEsJ4BND+K72cCQBvAdOo6MhawjDQr2xUKXVXj50=; b=hjecM9B46Y0O5tirCRFS3UNu9Au617Gc0YDCxBOuq14wrzFlPcvfKwM0Idk1oYHKdu iW3/gC4izYHxCOusqd1ROgwZIzo0Et4Lp2Gq58gfa1PfqWqCW0wz4R9TIFthPrwZgXAY o5Sjrr39KqEd7IvxpPwaTfCuaLk70xWOj0gEIy5zdOLp9e/o16vy1J4UrNKUBZ2qQfs6 q1XkqH+B5y3MHmaIj85QXXJLB4B/wZs3VTolUtBSfdgjdIx2TcMoWqZXNwPfSU8ycPRy l+ZRB9B6pJZLLhWCgJTpV2YnfXKhoT2dRUI0gzU4iWSlxl1MJASZ3SDyGEWjvOM0mnJ4 7k1g== X-Gm-Message-State: AOAM530TGQzWeeKhwosbiCNPdI7QtV5JOxdb667eCK37Sr3Lf3UCYBwa EBM+MdHRAI+x/YPE9HoQ9ZCh2wRihXyCQA== X-Google-Smtp-Source: ABdhPJyiViQeKu/a+h0h+gdSsdmRG85ooX1kCdp+FYA6Aj2iSV3nrrF2p5tiHhl3UR57e+rE2pEeYg== X-Received: by 2002:a17:906:ece1:: with SMTP id qt1mr3670348ejb.385.1619100636732; Thu, 22 Apr 2021 07:10:36 -0700 (PDT) Received: from [192.168.178.48] ([212.71.9.13]) by smtp.gmail.com with ESMTPSA id u15sm2291515edx.34.2021.04.22.07.10.36 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 22 Apr 2021 07:10:36 -0700 (PDT) Subject: Re: BUG #16976: server crash when deleting via a trigger on a foreign table To: Tom Lane Cc: Michael Paquier , pgsql-bugs@lists.postgresql.org References: <16976-abe0cb88252bc02e@postgresql.org> <756273.1619012414@sss.pgh.pa.us> <813ebc08-8f81-4efe-a5f2-caac938b7741@gmail.com> <821fb923-aaf5-ee3f-21d2-17158035dc64@gmail.com> <953012.1619099429@sss.pgh.pa.us> From: Herwig Goemans Message-ID: <81647b1a-c841-f7d8-fe92-8f01d72e5482@gmail.com> Date: Thu, 22 Apr 2021 16:10:36 +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: <953012.1619099429@sss.pgh.pa.us> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: nl-BE List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Ok,  I have a core dump file, It is not generated by a test of me, but that does not matter, the sql statement was launched by a colleage of mine and it generated a core dump. The file is 50MB (compressed) how do I get it to you ? Herwig On 22/04/2021 15:50, Tom Lane wrote: > Herwig Goemans writes: >> I think I have to get a stacktrace of the postgres server process , not >> of psql but I do not how to do that. > Right. The wiki page I pointed you to upthread has recipes for that. > > https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend > > regards, tom lane