Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1syRkY-00Grjv-0r for pgsql-general@arkaria.postgresql.org; Wed, 09 Oct 2024 08:08:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1syRkW-00FLs0-OK for pgsql-general@arkaria.postgresql.org; Wed, 09 Oct 2024 08:08:48 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sy2zp-003L1u-6o for pgsql-general@lists.postgresql.org; Tue, 08 Oct 2024 05:42:57 +0000 Received: from mail-lf1-x135.google.com ([2a00:1450:4864:20::135]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sy2zm-0034Ke-6Z for pgsql-general@postgresql.org; Tue, 08 Oct 2024 05:42:55 +0000 Received: by mail-lf1-x135.google.com with SMTP id 2adb3069b0e04-53988c54ec8so5953367e87.0 for ; Mon, 07 Oct 2024 22:42:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728366171; x=1728970971; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=BQ45D0adOHtoL2OccP7Ygqa4GJl69SmfykTMpZaYlUE=; b=BFJSci+SjbSj1vaBwHyvt50nLmCJJKczzaybFdNthicvMTyBaI9LH5W83I6S8/vbdj 8UfjkG1tkgU2tjReiwISuWTLHHcjqdEC10P1X5Xt6kK/pH4GTCORGwbu+negsvXq7ivf H/Er07R3/SiwvLlcbzGkyuEeOPxes2ReaXgaXQlzUM8DsiYtn3mmqc+diQIz1Qe1VgBZ r6/sFbDwJZZLOaYIfvYB/mYHKLqdU5tOoeDDKMmI3exOEBw7wSLZ3VxbQVbUoopX4qUg CzPTqdYV9lrmgTuKr+Vsd28lQ25cl3wlzvU6NbSdhwMD5Z+TOm0uMO0eQgqXsZHfZ3mr S7aA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728366171; x=1728970971; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=BQ45D0adOHtoL2OccP7Ygqa4GJl69SmfykTMpZaYlUE=; b=XJGBG9pPsYR2CSFVmdQrluHm7etXRd0H39YUvHBjow7k1RL8Q3vGwLKTRzCAHGFi94 EFRCcczRa5L+OhstF5csXimmL8SjeilwgDIa7pos60o/F0vwncYzyb5h/HJcF+K0S8ox J7UA94213Zpv8pmJTYhQqJAe5EVpFwm7sGddYFnA23qtAyTjSp/NRw8WNvwGgnEF2P8w FdpMmUTp2hMi1X+KWSO2LhxRHf9XVfzQDIrCo3Iije9s/nbxEnDbSc47GSoiUcer8Bju T/OjES1DMb15YI1/AoChmzy9WmSe57gmEmUHKhwNi94V8Hc5Pk5z7ynrt4Jf2Bu6VIxr VZgA== X-Gm-Message-State: AOJu0Yx9usSN9YTrhon4y5oCuqtVZPv3nr2c7BxvwLf+xgEZlH90TiKn 9VZ5yu/x5Ktk2FdxU0qY4HgoCiVqXczL27Sdbflqb6F7RxYfW9kYnxDDQUX6fOXWkgk3h1xCGC4 N1LMf75rx9FjE3IWd8C+nqWKZ+eE/RDQL X-Google-Smtp-Source: AGHT+IFVi2lBmVnHRcBIANHfjeAvBhBwiKhFW5gdQAECm96PAekfAzdH3hYiZ9TuhtR/9nxjNpYdmIvrhcEkb9Sstlw= X-Received: by 2002:a05:6512:b96:b0:539:9527:3d59 with SMTP id 2adb3069b0e04-539ab9f0f7dmr7281629e87.52.1728366170687; Mon, 07 Oct 2024 22:42:50 -0700 (PDT) MIME-Version: 1.0 From: Cassandra Thrift Date: Tue, 8 Oct 2024 11:12:35 +0530 Message-ID: Subject: pg_dump throwing segfault error during backup To: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="000000000000a54ebd0623f09b4b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a54ebd0623f09b4b Content-Type: text/plain; charset="UTF-8" Hello Team, We are facing a segfault issue while initiating backup with pg_dump. This is for Postgresql community version 12.5 and rhel 7.4 (PostgreSQL 12.5 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39), 64-bit) The below error is showing : from /var/log/message [root@USMS-PV-CRMDB2 log]# grep 'segfault' messages* messages:Sep 24 00:15:56 USMS-PV-CRMDB2 kernel: postgres[1535]: segfault at 23c0000 ip 00007f272c91f61d sp 00007ffe22636718 error 6 in libc-2.17.so [7f272c7d3000+1b8000] messages:Sep 25 00:14:59 USMS-PV-CRMDB2 kernel: postgres[4245]: segfault at 23c0000 ip 00007f272c91f61d sp 00007ffe22636718 error 6 in libc-2.17.so [7f272c7d3000+1b8000] messages-20240923:Sep 21 00:07:13 USMS-PV-CRMDB2 kernel: postgres[14743]: segfault at 23c0000 ip 00007f272c91f622 sp 00007ffe22636718 error 6 in libc-2.17.so[7f272c7d3000+1b8000] messages-20240923:Sep 22 00:06:53 USMS-PV-CRMDB2 kernel: postgres[392]: segfault at 23c0000 ip 00007f272c91f61d sp 00007ffe22636718 error 6 in libc-2.17.so[7f272c7d3000+1b8000] messages-20240923:Sep 23 00:16:07 USMS-PV-CRMDB2 kernel: postgres[28843]: segfault at 23c0000 ip 00007f272c91f622 sp 00007ffe22636718 error 6 in libc-2.17.so[7f272c7d3000+1b8000] From db log : 2024-09-26 00:47:05.312 +08 [9908] HINT: In a moment you should be able to reconnect to the database and repeat your command. 2024-09-26 00:47:05.306 +08 [10870] WARNING: terminating connection because of crash of another server process 2024-09-26 00:47:05.306 +08 [10870] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. We fond the timing which shows database backup is getting invoked at the time. So we had to stop backup (pg_backup) we are manually taking table data currently. Core dump also generated however RedHat refused to analyze this saying it is third party product. Kindly let us know if this is a bug for the version as it is too old and if the core dump can be analyzed somehow as it is in binary. Regards Somraj Chakrabarty --000000000000a54ebd0623f09b4b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Team,

We are facing a segfault is= sue while initiating backup with pg_dump.
This is for Postgresql = community version 12.5 and rhel 7.4 (PostgreSQL 12.5 on x86_64-pc-linux-gnu= , compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39), 64-bit)

The below error is showing :

from= /var/log/message

[root@USMS-PV-= CRMDB2 log]# grep 'segfault' messages*
messages:Sep 24 00:15:56 = USMS-PV-CRMDB2 kernel: postgres[1535]: segfault at 23c0000 ip 00007f272c91f= 61d sp 00007ffe22636718 error 6 in=C2=A0libc-2.17.so[7f272c7d3000+1b8000]
messages:Sep 25 00= :14:59 USMS-PV-CRMDB2 kernel: postgres[4245]: segfault at 23c0000 ip 00007f= 272c91f61d sp 00007ffe22636718 error 6 in=C2=A0libc-2.17.so[7f272c7d3000+1b8000]
messages-20= 240923:Sep 21 00:07:13 USMS-PV-CRMDB2 kernel: postgres[14743]: segfault at = 23c0000 ip 00007f272c91f622 sp 00007ffe22636718 error 6 in=C2=A0libc-2.17.so[7f272c7d3000+1b800= 0]
messages-20240923:Sep 22 00:06:53 USMS-PV-CRMDB2 kernel: postgres[392= ]: segfault at 23c0000 ip 00007f272c91f61d sp 00007ffe22636718 error 6 in= =C2=A0libc-2.17.so[7= f272c7d3000+1b8000]
messages-20240923:Sep 23 00:16:07 USMS-PV-CRMDB2 ker= nel: postgres[28843]: segfault at 23c0000 ip 00007f272c91f622 sp 00007ffe22= 636718 error 6 in=C2=A0l= ibc-2.17.so[7f272c7d3000+1b8000]


From db log :
2024-09-26 00:47:05.312 +08 [9908] HINT:=C2= =A0 In a moment you should be able to reconnect to the database and repeat = your command.
2024-09-26 00:47:05.306 +08 [10870] WARNING:=C2=A0 termina= ting connection because of crash of another server process
2024-09-26 00= :47:05.306 +08 [10870] DETAIL:=C2=A0 The postmaster has commanded this serv= er process to roll back the current transaction and exit, because another s= erver process exited abnormally and possibly corrupted shared memory.

W= e fond the timing which shows database backup is getting invoked at the tim= e. So we had to stop backup (pg_backup)
=
we are manually taking table data currently.

Core dump also generated however RedHat refused to analyze= this saying it is third party product.

Kindly let= us know if this is a bug for the version as it is too old and if the core = dump can be analyzed somehow as it is in binary.

R= egards
Somraj Chakrabarty
--000000000000a54ebd0623f09b4b--