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 1pEtpm-0001nD-2Q for pgsql-bugs@arkaria.postgresql.org; Mon, 09 Jan 2023 15:13:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pEtpk-0003uV-JE for pgsql-bugs@arkaria.postgresql.org; Mon, 09 Jan 2023 15:13:08 +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 1pEtpk-0003uM-B4 for pgsql-bugs@lists.postgresql.org; Mon, 09 Jan 2023 15:13:08 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pEtpi-0002Ot-5q for pgsql-bugs@lists.postgresql.org; Mon, 09 Jan 2023 15:13:07 +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 309FD2484092324; Mon, 9 Jan 2023 10:13:03 -0500 From: Tom Lane To: giulio.ferrari@cambieri.it cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17743: Bad RIP VALUE In-reply-to: <17743-7a91f7932af59965@postgresql.org> References: <17743-7a91f7932af59965@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Mon, 09 Jan 2023 12:55:32 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4092322.1673277181.1@sss.pgh.pa.us> Date: Mon, 09 Jan 2023 10:13:01 -0500 Message-ID: <4092323.1673277181@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: > On the installation in object I am experiencing this error: The stack trace you show is entirely within the kernel, so I think you need to be reporting this as a kernel bug not a Postgres bug. Looks like something goes wrong when we call fsync(). regards, tom lane