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 1syXe5-000edY-Pu for pgsql-general@arkaria.postgresql.org; Wed, 09 Oct 2024 14:26:34 +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 1syXd6-0027Vh-ST for pgsql-general@arkaria.postgresql.org; Wed, 09 Oct 2024 14:25:33 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1syXd6-0027VY-Cg for pgsql-general@lists.postgresql.org; Wed, 09 Oct 2024 14:25:32 +0000 Received: from mail-oa1-x32.google.com ([2001:4860:4864:20::32]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1syXd2-000AkH-Us for pgsql-general@postgresql.org; Wed, 09 Oct 2024 14:25:32 +0000 Received: by mail-oa1-x32.google.com with SMTP id 586e51a60fabf-277e6002b7dso1951489fac.1 for ; Wed, 09 Oct 2024 07:25:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728483927; x=1729088727; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=HdZoUSNIOPapeTwHxYiEewcpZC1ACe/c75bF8KUYEVU=; b=kh5hqUNbX9awyGrel40x8a6+F9EkktxGdNhbg5sa22zJacM/qzNoJ0wQVJSk4anfze egH99lPxzQOI4ppogdnG+pYD4Wr4CQZYEWCoEJ6hKLEpraKRv3bFHEclrhRO+jADCYD2 aurJnz2blgfTkpKsrDK5f32gedx8nZN4+mzFYgpTcqn5CGEniDJsVOhS3EqtmqGciELD BPgK4Tn/j6WFm/R9vfm76RR3/Y7zpxZi+u1ubkztBPokR5onycU8k6hgfkEeuw3J2EIf AeS7hqJk04r6Nqky5z5VgCXaKKsSw3tgGpjNP1dGhnCgQcKt8jgJnvVivBYxRzqoIFex 8A3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728483927; x=1729088727; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=HdZoUSNIOPapeTwHxYiEewcpZC1ACe/c75bF8KUYEVU=; b=ThxFfX185z1GJd9AgdKV4qCjy1hAGBo6W+PyFgC3PwCwg+WrlYqu75o3ysiiJqQliA EZDk+iwZ5o0UOd22oypg+yUaf5jYITbERUW32Oovyq9JyuZgIfxXM3f05Q0L+2F/9dJQ MohJtTQpDqfh9ZgtiTjcKBofrXvMvej3tkh8afTFOd0zNgeZbtBb9MB2nodJpTfhtL8d lm8+Ose+x5ibnAqkNV83smYXiga0bwUS3eAgH5u3chsJzgNbg/Zhp73aXV/errLsqI0N x7M15LgygeufbQ7klYXzO93KTLVOYIyjD3fHHR2mV4hSBhlkuL/lqVXKcOBFgrQNjXv1 xriQ== X-Gm-Message-State: AOJu0YxI+M11jPqeq4uG/9U+pQpN4i8XabZPcg/uG3gKboheMYgos06c cqxLV+INand+wrxAg10SnKwThV3Ik97a/TIDY42AAd1Lz5jfVPshxHjsNRFVaGRcVaX8OZWGDUK y/oi7+x1X5wDRnFXdHIlE0B2BTBy1LoM/ X-Google-Smtp-Source: AGHT+IHA2aHrYpDMemNks/Ct4CB0wayaFT26qpiXo9nmJubn8la4JWvseDs7zOM9TBx+HBh3/8v9ATlL/WjdAcVxc3g= X-Received: by 2002:a05:6870:a119:b0:261:1f7d:cf71 with SMTP id 586e51a60fabf-288344c3035mr1547067fac.34.1728483927226; Wed, 09 Oct 2024 07:25:27 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Wed, 9 Oct 2024 10:25:16 -0400 Message-ID: Subject: Re: pg_dump throwing segfault error during backup To: pgsql-general Content-Type: multipart/alternative; boundary="0000000000007b832b06240c06f0" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000007b832b06240c06f0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Oct 9, 2024 at 4:08=E2=80=AFAM Cassandra Thrift wrote: > 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 Ha= t > 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.s= o > [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.s= o > [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, becaus= e > 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. > PG 12.5 is missing *four years* of patches, and RHEL 7.4 is also far behind the current 7.9. https://www.postgresql.org/docs/release/ tells you what's been done to v12 in every patch release. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. crustacean! --0000000000007b832b06240c06f0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Oct 9, 2024 at 4:08=E2=80=AFAM Ca= ssandra Thrift <cssndrthrift@g= mail.com> wrote:
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 (Pos= tgreSQL 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 show= ing :

from /var/log/message

[root@USMS-PV-CRMDB2 log]# grep 'segfault' mes= sages*
messages:Sep 24 00:15:56 USMS-PV-CRMDB2 kernel: postgres[1535]: s= egfault at 23c0000 ip 00007f272c91f61d sp 00007ffe22636718 error 6 in=C2=A0= libc-2.17.so[7f272c7= d3000+1b8000]
messages:Sep 25 00:14:59 USMS-PV-CRMDB2 kernel: postgres[4= 245]: segfault at 23c0000 ip 00007f272c91f61d sp 00007ffe22636718 error 6 i= n=C2=A0libc-2.17.so[= 7f272c7d3000+1b8000]
messages-20240923:Sep 21 00:07:13 USMS-PV-CRMDB2 ke= rnel: postgres[14743]: segfault at 23c0000 ip 00007f272c91f622 sp 00007ffe2= 2636718 error 6 in=C2=A0= libc-2.17.so[7f272c7d3000+1b8000]
messages-20240923:Sep 22 00:06:53 = USMS-PV-CRMDB2 kernel: postgres[392]: segfault at 23c0000 ip 00007f272c91f6= 1d sp 00007ffe22636718 error 6 in=C2=A0libc-2.17.so[7f272c7d3000+1b8000]
messages-20240923:S= ep 23 00:16:07 USMS-PV-CRMDB2 kernel: postgres[28843]: segfault at 23c0000 = ip 00007f272c91f622 sp 00007ffe22636718 error 6 in=C2=A0libc-2.17.so[7f272c7d3000+1b8000]

F= rom db log :

2024-09-26 0= 0:47:05.312 +08 [9908] HINT:=C2=A0 In a moment you should be able to reconn= ect to the database and repeat your command.
2024-09-26 00:47:05.306 +08= [10870] WARNING:=C2=A0 terminating connection because of crash of another = server process
2024-09-26 00:47:05.306 +08 [10870] DETAIL:=C2=A0 The pos= tmaster has commanded this server process to roll back the current transact= ion and exit, because another server process exited abnormally and possibly= corrupted shared memory.


We fond the timing which shows database backu= p 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 ho= wever 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 bin= ary.

PG 12.5 i= s missing four years=C2=A0of patches,=C2=A0and RHEL 7.4 is also far = behind the current 7.9.

https://www.postgresql.org/docs/release/ tel= ls you what's been done to v12 in every patch release.
--
Death to <Redacted>, an= d butter sauce.
Don't boil me, I'm still alive.
&l= t;Redacted> crustacean!
--0000000000007b832b06240c06f0--