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 1lZZFw-0002xN-EW for pgsql-bugs@arkaria.postgresql.org; Thu, 22 Apr 2021 13:20:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lZZFu-00059Q-5B for pgsql-bugs@arkaria.postgresql.org; Thu, 22 Apr 2021 13:20:30 +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 1lZZFt-00059J-Se for pgsql-bugs@lists.postgresql.org; Thu, 22 Apr 2021 13:20:29 +0000 Received: from mail-ej1-x62e.google.com ([2a00:1450:4864:20::62e]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lZZFn-0003z1-OS for pgsql-bugs@lists.postgresql.org; Thu, 22 Apr 2021 13:20:28 +0000 Received: by mail-ej1-x62e.google.com with SMTP id sd23so60098896ejb.12 for ; Thu, 22 Apr 2021 06:20:23 -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=mc2qq28Ewn82QQ3sJbPaaHmJvVSpnxqMyCiJW5o5Mr4=; b=ZCBq/gIRXuvR2hfuph6XZZQ7GL+7RUBZFj9LU4+saOajqhq+zPptvGeKLoE+3ge4oC rt20kgw97hwfrm7EEEyRWdeWnLPtGsuex8+dY2S+ufX6hQJD7B4EaLhXGsnoutK0mlkD 3h9VZ5fo4HLcF+p+wY21UDtVZbn1kL51wsueQ8mf+K41/Gd0D2aclauJWdWSk1FWssVy TkUMT9wG/PBczawMmsJjoRRKLR070o1NMp2yYtyQ6vLt6g6h72o/1vO6TM1AkNTin8fl pBcqsSZB9tmdB9j1ob4zY0rAFOzINa2S3GOil3Jgj3O8rdBBhCKU9yfPjpNBOYy1FEGa 84yA== 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=mc2qq28Ewn82QQ3sJbPaaHmJvVSpnxqMyCiJW5o5Mr4=; b=adIsZMbM7DCu6/41E5Q5stq5SuvmFDwAlqc+T67tweweX0sFot5/PNxHaiTVlOCPZh XYqI1QWQxY7LZ7Av67MfX47NGV5MIOlyMi2/naccSaf/Awcp3hfxqYcwYhj9WvTCppYF bd5yHi/b8ZeA8QhEhYkLYVZD59ynEle9EQn87HLiVQ1gnwioYz+nOsRselkT/tbHV/7j tHQSY++DhoJf78YSVuvkyu1Lnu1WZtooUM8cQWZJHuPLpMt/0O3exFvlKgfkJeOAQomU qtQHZHzfw92wy/Z/JfHarj7LqeZHaH3sO1HvQIkPmuEE+Cpl/i+DdDHbqU0H95Pxf+vA oohg== X-Gm-Message-State: AOAM531qMHOb3R0nyyuVOt5SYAisLMrDnofnqBt40RQ0tCXByfpEF7yW VbqWr1KWRoeXIlrxLotA774= X-Google-Smtp-Source: ABdhPJxaIrC8d2tPvtdtkNo3jAEFHedjotx8Au1LPs1iexML1XANCrRfcBb6gp2DhYB8tCjc4SFxVQ== X-Received: by 2002:a17:906:390d:: with SMTP id f13mr3389880eje.328.1619097622058; Thu, 22 Apr 2021 06:20:22 -0700 (PDT) Received: from [192.168.178.48] ([212.71.9.13]) by smtp.gmail.com with ESMTPSA id n11sm1878854ejg.43.2021.04.22.06.20.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 22 Apr 2021 06:20:21 -0700 (PDT) Subject: Re: BUG #16976: server crash when deleting via a trigger on a foreign table To: Michael Paquier Cc: Tom Lane , pgsql-bugs@lists.postgresql.org, PG Bug reporting form References: <16976-abe0cb88252bc02e@postgresql.org> <756273.1619012414@sss.pgh.pa.us> <813ebc08-8f81-4efe-a5f2-caac938b7741@gmail.com> From: Herwig Goemans Message-ID: <821fb923-aaf5-ee3f-21d2-17158035dc64@gmail.com> Date: Thu, 22 Apr 2021 15:20:21 +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: Content-Type: text/plain; charset=windows-1252; 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 Hi, I am not sure what you mean, I am not a developer. What I did: started gdb and then: (gdb) set pagination 0 (gdb) attach 84465 Attaching to process 84465 0x00007f58bd33143e in __libc_read (fd=0, buf=0x7ffe09e53c80, nbytes=1) at ../sysdeps/unix/sysv/linux/read.c:27 27      ../sysdeps/unix/sysv/linux/read.c: No such file or directory. (gdb) continue Continuing. [Inferior 1 (process 84465) exited normally] (gdb) backtrace full No stack. (gdb) quit that's it. I think I have to get a stacktrace of the postgres server process , not of psql but I do not how to do that. Herwig On 22/04/2021 12:52, Michael Paquier wrote: > On Thu, Apr 22, 2021 at 12:09:44PM +0200, Herwig Goemans wrote: >> Anyway, with the trigger in place we encounter PG server crashes. >> >> I am having trouble collection a trace file because when I attach gdb to the >> process: >> >> 0x00007f99b46f7a07 in epoll_wait (epfd=5, events=0x561321b40630, >> maxevents=maxevents@entry=1, timeout=timeout@entry=-1) at >> ../sysdeps/unix/sysv/linux/epoll_wait.c:30 >> 30      ../sysdeps/unix/sysv/linux/epoll_wait.c: No such file or directory. >> (gdb) quit > What does a simple "bt" print? > -- > Michael