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 1pprRh-0005su-FZ for pgsql-bugs@arkaria.postgresql.org; Fri, 21 Apr 2023 14:09:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pprRg-0001s9-D6 for pgsql-bugs@arkaria.postgresql.org; Fri, 21 Apr 2023 14:09:04 +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 1pprRg-0001s0-4K for pgsql-bugs@lists.postgresql.org; Fri, 21 Apr 2023 14:09:04 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pprRd-0015WL-Oc for pgsql-bugs@lists.postgresql.org; Fri, 21 Apr 2023 14:09:02 +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 33LE90BM3337006; Fri, 21 Apr 2023 10:09:00 -0400 From: Tom Lane To: vaclav.pink@tietoevry.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17906: Segmentation fault and database crash during procedure call In-reply-to: <17906-fefd777fbd04daa5@postgresql.org> References: <17906-fefd777fbd04daa5@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Fri, 21 Apr 2023 10:19:03 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3337004.1682086140.1@sss.pgh.pa.us> Date: Fri, 21 Apr 2023 10:09:00 -0400 Message-ID: <3337005.1682086140@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form writes: > we are fighting more than 3 weeks with error: server process (PID 10028) was > terminated by signal 11: Segmentation fault > This error occur when I call db procedure (whole procedure is below). Can't help you with such an incomplete bug report. If you could reduce the problem to a self-contained test case, we'd be happy to look at it. See https://wiki.postgresql.org/wiki/Guide_to_reporting_problems regards, tom lane