agora inbox for pgsql-admin@postgresql.org
help / color / mirror / Atom feedUrgent: Segmentation Fault in PostgreSQL postmaster Process
16+ messages / 6 participants
[nested] [flat]
* Urgent: Segmentation Fault in PostgreSQL postmaster Process
@ 2024-06-16 23:49 Veerendra Pulapa <veerendra.pulapa@ashnik.com>
0 siblings, 3 replies; 16+ messages in thread
From: Veerendra Pulapa @ 2024-06-16 23:49 UTC (permalink / raw)
To: pgsql-admin; pgsql-admin@lists.postgresql.org
Dear Team,
I am experiencing a segmentation fault issue with the postmaster process of
our PostgreSQL database, and I am seeking your assistance. Below are the
details of the error and our system configuration.
*Issue Description*
We encountered a segmentation fault in the postmaster process of our
PostgreSQL instance. The relevant system log entry is as follows:
*DB Logs:*
LOG: restartpoint starting: time
LOG: startup process (PID 21704) was terminated by signal 11: Segmentation
fault
LOG: terminating any other active server processes
LOG: database system is shut down
LOG: starting PostgreSQL 13.2 on x86_64-pc-linux-gnu, compiled by gcc
(GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit
LOG: listening on IPv4 address "0.0.0.0", port 5432
LOG: listening on IPv6 address "::", port 5432
LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
LOG: listening on Unix socket "/tmp/.s.PGSQL.5432"
LOG: database system was interrupted while in recovery at log time
2024-06-16 19:37:48 +08
HINT: If this has occurred more than once some data might be corrupted and
you might need to choose an earlier recovery target.
*OS logs:*
kernel: postmaster[7844]: segfault at 2dd736b ip 00000000004ddc75 sp
00007ffe0e9c3490 error 6 in postgres[400000+73e000]
*PostgreSQL Version and Environment:*
PostgreSQL Version: 13.2
Operating System: rhel 7.9
Kernel Version: 3.10.0-1160.118.1.el7.x86_64
System Specifications: [32 vCPU, 250GB]
Br,
Veerendra Pulapa | Technical Consultant
M: +91-9949349894 | www.ashnik.com
<https://www.linkedin.com/company/ashnik-pte-ltd/;
<https://www.facebook.com/AshnikBiz;
<https://www.youtube.com/user/ashnikbiz;
<https://www.instagram.com/ashnikbiz/; <https://twitter.com/Ashnikbiz;
--
*________________________________________________________________________________________
*_This email may contain confidential, privileged or copyright material and
is solely for the use of the intended recipient(s). If you are not the
rightful recipient of this email, please delete this email immediately and
inform the recipient.
_
*
*
^ permalink raw reply [nested|flat] 16+ messages in thread
* RE: Urgent: Segmentation Fault in PostgreSQL postmaster Process
@ 2024-06-17 03:02 lennam@incisivetechgroup.com
parent: Veerendra Pulapa <veerendra.pulapa@ashnik.com>
2 siblings, 1 reply; 16+ messages in thread
From: lennam@incisivetechgroup.com @ 2024-06-17 03:02 UTC (permalink / raw)
To: 'Veerendra Pulapa' <veerendra.pulapa@ashnik.com>; pgsql-admin; pgsql-admin@lists.postgresql.org
Check if any disk issues
Storage is local or SAN , if SAN see if any hiccups to communicate SAN
Check disk space usage
From: Veerendra Pulapa <veerendra.pulapa@ashnik.com>
Sent: Sunday, June 16, 2024 7:49 PM
To: pgsql-admin <pgsql-admin@postgresql.org>; pgsql-admin@lists.postgresql.org
Subject: Urgent: Segmentation Fault in PostgreSQL postmaster Process
Dear Team,
I am experiencing a segmentation fault issue with the postmaster process of our PostgreSQL database, and I am seeking your assistance. Below are the details of the error and our system configuration.
Issue Description
We encountered a segmentation fault in the postmaster process of our PostgreSQL instance. The relevant system log entry is as follows:
DB Logs:
LOG: restartpoint starting: time
LOG: startup process (PID 21704) was terminated by signal 11: Segmentation fault
LOG: terminating any other active server processes
LOG: database system is shut down
LOG: starting PostgreSQL 13.2 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit
LOG: listening on IPv4 address "0.0.0.0", port 5432
LOG: listening on IPv6 address "::", port 5432
LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
LOG: listening on Unix socket "/tmp/.s.PGSQL.5432"
LOG: database system was interrupted while in recovery at log time 2024-06-16 19:37:48 +08
HINT: If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target.
OS logs:
kernel: postmaster[7844]: segfault at 2dd736b ip 00000000004ddc75 sp 00007ffe0e9c3490 error 6 in postgres[400000+73e000]
PostgreSQL Version and Environment:
PostgreSQL Version: 13.2
Operating System: rhel 7.9
Kernel Version: 3.10.0-1160.118.1.el7.x86_64
System Specifications: [32 vCPU, 250GB]
Br,
Veerendra Pulapa | Technical Consultant
M: +91-9949349894 | www.ashnik.com <http://www.ashnik.com;
<https://ci3.googleusercontent.com/mail-sig/AIorK4xvfK9qSVZpXOLltt7nySqTlW3dSlhYzLdhhavPD4rhwxaAmZmru...;
<https://www.linkedin.com/company/ashnik-pte-ltd/; <https://www.facebook.com/AshnikBiz; <https://www.youtube.com/user/ashnikbiz; <https://www.instagram.com/ashnikbiz/; <https://twitter.com/Ashnikbiz;
______________________________________________________________________________________
This email may contain confidential, privileged or copyright material and is solely for the use of the intended recipient(s). If you are not the rightful recipient of this email, please delete this email immediately and inform the recipient.
^ permalink raw reply [nested|flat] 16+ messages in thread
* Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
@ 2024-06-17 05:10 Vijaykumar Jain <vijaykumarjain.github@gmail.com>
parent: Veerendra Pulapa <veerendra.pulapa@ashnik.com>
2 siblings, 1 reply; 16+ messages in thread
From: Vijaykumar Jain @ 2024-06-17 05:10 UTC (permalink / raw)
To: Veerendra Pulapa <veerendra.pulapa@ashnik.com>; +Cc: pgsql-admin; Pgsql-admin <pgsql-admin@lists.postgresql.org>
On Mon, Jun 17, 2024, 5:19 AM Veerendra Pulapa <veerendra.pulapa@ashnik.com>
wrote:
*OS logs:*
> kernel: postmaster[7844]: segfault at 2dd736b ip 00000000004ddc75 sp
> 00007ffe0e9c3490 error 6 in postgres[400000+73e000]
>
> *PostgreSQL Version and Environment:*
> PostgreSQL Version: 13.2
> Operating System: rhel 7.9
> Kernel Version: 3.10.0-1160.118.1.el7.x86_64
> System Specifications: [32 vCPU, 250GB]
>
is it possible for you to do a minor upgrade to latest 13.12 version.
it should be a minor upgrade , upgrade and restart might be all you need.
iirc there were bugs in older 13.x versions that were fixed in later
versions.
>
^ permalink raw reply [nested|flat] 16+ messages in thread
* Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
@ 2024-06-17 05:14 Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>
parent: Veerendra Pulapa <veerendra.pulapa@ashnik.com>
2 siblings, 1 reply; 16+ messages in thread
From: Achilleas Mantzios @ 2024-06-17 05:14 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Στις 17/6/24 02:49, ο/η Veerendra Pulapa έγραψε:
> Dear Team,
>
> I am experiencing a segmentation fault issue with the postmaster
> process of our PostgreSQL database, and I am seeking your assistance.
> Below are the details of the error and our system configuration.
>
> *Issue Description*
> We encountered a segmentation fault in the postmaster process of our
> PostgreSQL instance. The relevant system log entry is as follows:
>
> *DB Logs:*
> LOG: restartpoint starting: time
> LOG: startup process (PID 21704) was terminated by signal 11:
> Segmentation fault
> LOG: terminating any other active server processes
> LOG: database system is shut down
> LOG: starting PostgreSQL 13.2 on x86_64-pc-linux-gnu, compiled by gcc
> (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit
> LOG: listening on IPv4 address "0.0.0.0", port 5432
> LOG: listening on IPv6 address "::", port 5432
> LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
> LOG: listening on Unix socket "/tmp/.s.PGSQL.5432"
> LOG: database system was interrupted while in recovery at log time
> 2024-06-16 19:37:48 +08
> HINT: If this has occurred more than once some data might be
> corrupted and you might need to choose an earlier recovery target.
This runs as a primary right? The logs indicate that the postmaster had
already crashed and was trying to recover while it threw another segfault.
Give us some historical background of any events that happened in the
course of your installation that might be of any interest. Such as, how
often do you get the problem, how long are you having this problem, what
did change before the problem started to appear (software/hardware).
IME, such errors could be due to either faulty CPU or memory. I'd run a
memtest and run diagnostics (BIOS), check temperatures, etc
>
> *OS logs:*
> kernel: postmaster[7844]: segfault at 2dd736b ip 00000000004ddc75 sp
> 00007ffe0e9c3490 error 6 in postgres[400000+73e000]
>
> *PostgreSQL Version and Environment:*
> PostgreSQL Version: 13.2
> Operating System: rhel 7.9
> Kernel Version: 3.10.0-1160.118.1.el7.x86_64
> System Specifications: [32 vCPU, 250GB]
>
> Br,
> Veerendra Pulapa | Technical Consultant
> M: +91-9949349894 | www.ashnik.com <http://www.ashnik.com;
>
>
> <https://www.linkedin.com/company/ashnik-pte-ltd/;
> <https://www.facebook.com/AshnikBiz;
> <https://www.youtube.com/user/ashnikbiz;
> <https://www.instagram.com/ashnikbiz/; <https://twitter.com/Ashnikbiz;
>
>
> /
> /______________________________________________________________________________________/
> /This email may contain confidential, privileged or copyright material
> and is solely for the use of the intended recipient(s). If you are not
> the rightful recipient of this email, please delete this email
> immediately and inform the recipient. /
> /
> /
> /
--
Achilleas Mantzios
IT DEV - HEAD
IT DEPT
Dynacom Tankers Mgmt (as agents only)
^ permalink raw reply [nested|flat] 16+ messages in thread
* Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
@ 2024-06-17 12:54 Veerendra Pulapa <veerendra.pulapa@ashnik.com>
parent: lennam@incisivetechgroup.com
0 siblings, 0 replies; 16+ messages in thread
From: Veerendra Pulapa @ 2024-06-17 12:54 UTC (permalink / raw)
To: lennam@incisivetechgroup.com; +Cc: pgsql-admin; pgsql-admin@lists.postgresql.org
I have checked with the system team as per them there is no issue with the
disk and it is SAN. Did not see any issue with communication.
Br,
Veerendra Pulapa | Technical Consultant
M: +91-9949349894 | www.ashnik.com
<https://www.linkedin.com/company/ashnik-pte-ltd/;
<https://www.facebook.com/AshnikBiz;
<https://www.youtube.com/user/ashnikbiz;
<https://www.instagram.com/ashnikbiz/; <https://twitter.com/Ashnikbiz;
On Mon, Jun 17, 2024 at 8:32 AM <lennam@incisivetechgroup.com> wrote:
> Check if any disk issues
>
> Storage is local or SAN , if SAN see if any hiccups to communicate SAN
>
> Check disk space usage
>
>
>
>
>
>
>
> *From:* Veerendra Pulapa <veerendra.pulapa@ashnik.com>
> *Sent:* Sunday, June 16, 2024 7:49 PM
> *To:* pgsql-admin <pgsql-admin@postgresql.org>;
> pgsql-admin@lists.postgresql.org
> *Subject:* Urgent: Segmentation Fault in PostgreSQL postmaster Process
>
>
>
> Dear Team,
>
>
>
> I am experiencing a segmentation fault issue with the postmaster process
> of our PostgreSQL database, and I am seeking your assistance. Below are the
> details of the error and our system configuration.
>
>
>
> *Issue Description*
>
> We encountered a segmentation fault in the postmaster process of our
> PostgreSQL instance. The relevant system log entry is as follows:
>
>
>
> *DB Logs:*
>
> LOG: restartpoint starting: time
>
> LOG: startup process (PID 21704) was terminated by signal 11:
> Segmentation fault
>
> LOG: terminating any other active server processes
>
> LOG: database system is shut down
>
> LOG: starting PostgreSQL 13.2 on x86_64-pc-linux-gnu, compiled by gcc
> (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit
>
> LOG: listening on IPv4 address "0.0.0.0", port 5432
>
> LOG: listening on IPv6 address "::", port 5432
>
> LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
>
> LOG: listening on Unix socket "/tmp/.s.PGSQL.5432"
>
> LOG: database system was interrupted while in recovery at log time
> 2024-06-16 19:37:48 +08
>
> HINT: If this has occurred more than once some data might be corrupted
> and you might need to choose an earlier recovery target.
>
>
>
> *OS logs:*
>
> kernel: postmaster[7844]: segfault at 2dd736b ip 00000000004ddc75 sp
> 00007ffe0e9c3490 error 6 in postgres[400000+73e000]
>
>
>
> *PostgreSQL Version and Environment:*
>
> PostgreSQL Version: 13.2
>
> Operating System: rhel 7.9
>
> Kernel Version: 3.10.0-1160.118.1.el7.x86_64
>
> System Specifications: [32 vCPU, 250GB]
>
>
>
> Br,
>
> Veerendra Pulapa | Technical Consultant
>
> M: +91-9949349894 | www.ashnik.com
>
> <https://www.linkedin.com/company/ashnik-pte-ltd/;
> <https://www.facebook.com/AshnikBiz;
> <https://www.youtube.com/user/ashnikbiz;
> <https://www.instagram.com/ashnikbiz/; <https://twitter.com/Ashnikbiz;
>
>
>
>
> *______________________________________________________________________________________*
>
> *This email may contain confidential, privileged or copyright material and
> is solely for the use of the intended recipient(s). If you are not the
> rightful recipient of this email, please delete this email immediately and
> inform the recipient. *
>
>
>
--
*________________________________________________________________________________________
*_This email may contain confidential, privileged or copyright material and
is solely for the use of the intended recipient(s). If you are not the
rightful recipient of this email, please delete this email immediately and
inform the recipient.
_
*
*
^ permalink raw reply [nested|flat] 16+ messages in thread
* Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
@ 2024-06-17 12:55 Veerendra Pulapa <veerendra.pulapa@ashnik.com>
parent: Vijaykumar Jain <vijaykumarjain.github@gmail.com>
0 siblings, 0 replies; 16+ messages in thread
From: Veerendra Pulapa @ 2024-06-17 12:55 UTC (permalink / raw)
To: Vijaykumar Jain <vijaykumarjain.github@gmail.com>; +Cc: pgsql-admin; Pgsql-admin <pgsql-admin@lists.postgresql.org>
Where will we get PostgreSQL bug reports?
Br,
Veerendra Pulapa | Technical Consultant
M: +91-9949349894 | www.ashnik.com
<https://www.linkedin.com/company/ashnik-pte-ltd/;
<https://www.facebook.com/AshnikBiz;
<https://www.youtube.com/user/ashnikbiz;
<https://www.instagram.com/ashnikbiz/; <https://twitter.com/Ashnikbiz;
On Mon, Jun 17, 2024 at 10:40 AM Vijaykumar Jain <
vijaykumarjain.github@gmail.com> wrote:
>
>
> On Mon, Jun 17, 2024, 5:19 AM Veerendra Pulapa <
> veerendra.pulapa@ashnik.com> wrote:
>
>
> *OS logs:*
>> kernel: postmaster[7844]: segfault at 2dd736b ip 00000000004ddc75 sp
>> 00007ffe0e9c3490 error 6 in postgres[400000+73e000]
>>
>> *PostgreSQL Version and Environment:*
>> PostgreSQL Version: 13.2
>> Operating System: rhel 7.9
>> Kernel Version: 3.10.0-1160.118.1.el7.x86_64
>> System Specifications: [32 vCPU, 250GB]
>>
>
> is it possible for you to do a minor upgrade to latest 13.12 version.
> it should be a minor upgrade , upgrade and restart might be all you need.
> iirc there were bugs in older 13.x versions that were fixed in later
> versions.
>
>
>
>>
--
*________________________________________________________________________________________
*_This email may contain confidential, privileged or copyright material and
is solely for the use of the intended recipient(s). If you are not the
rightful recipient of this email, please delete this email immediately and
inform the recipient.
_
*
*
^ permalink raw reply [nested|flat] 16+ messages in thread
* Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
@ 2024-06-17 13:00 Veerendra Pulapa <veerendra.pulapa@ashnik.com>
parent: Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>
0 siblings, 1 reply; 16+ messages in thread
From: Veerendra Pulapa @ 2024-06-17 13:00 UTC (permalink / raw)
To: Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>; +Cc: pgsql-admin@lists.postgresql.org
The signal 11 error reported only on the standby node. We have two nodes,
one master and one standby. And Virtual machines are hosted in azure.
We have upgraded the OS from 7.x to 8.x after the upgrade we have
observed some discrepancy then we rollback the OS. Even after rollback we
are also facing the same problem.
Br,
Veerendra Pulapa | Technical Consultant
M: +91-9949349894 | www.ashnik.com
<https://www.linkedin.com/company/ashnik-pte-ltd/;
<https://www.facebook.com/AshnikBiz;
<https://www.youtube.com/user/ashnikbiz;
<https://www.instagram.com/ashnikbiz/; <https://twitter.com/Ashnikbiz;
On Mon, Jun 17, 2024 at 10:44 AM Achilleas Mantzios <
a.mantzios@cloud.gatewaynet.com> wrote:
> Στις 17/6/24 02:49, ο/η Veerendra Pulapa έγραψε:
>
> Dear Team,
>
> I am experiencing a segmentation fault issue with the postmaster process
> of our PostgreSQL database, and I am seeking your assistance. Below are the
> details of the error and our system configuration.
>
> *Issue Description*
> We encountered a segmentation fault in the postmaster process of our
> PostgreSQL instance. The relevant system log entry is as follows:
>
> *DB Logs:*
> LOG: restartpoint starting: time
> LOG: startup process (PID 21704) was terminated by signal 11:
> Segmentation fault
> LOG: terminating any other active server processes
> LOG: database system is shut down
> LOG: starting PostgreSQL 13.2 on x86_64-pc-linux-gnu, compiled by gcc
> (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit
> LOG: listening on IPv4 address "0.0.0.0", port 5432
> LOG: listening on IPv6 address "::", port 5432
> LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
> LOG: listening on Unix socket "/tmp/.s.PGSQL.5432"
> LOG: database system was interrupted while in recovery at log time
> 2024-06-16 19:37:48 +08
> HINT: If this has occurred more than once some data might be corrupted
> and you might need to choose an earlier recovery target.
>
> This runs as a primary right? The logs indicate that the postmaster had
> already crashed and was trying to recover while it threw another segfault.
>
> Give us some historical background of any events that happened in the
> course of your installation that might be of any interest. Such as, how
> often do you get the problem, how long are you having this problem, what
> did change before the problem started to appear (software/hardware).
>
> IME, such errors could be due to either faulty CPU or memory. I'd run a
> memtest and run diagnostics (BIOS), check temperatures, etc
>
>
> *OS logs:*
> kernel: postmaster[7844]: segfault at 2dd736b ip 00000000004ddc75 sp
> 00007ffe0e9c3490 error 6 in postgres[400000+73e000]
>
> *PostgreSQL Version and Environment:*
> PostgreSQL Version: 13.2
> Operating System: rhel 7.9
> Kernel Version: 3.10.0-1160.118.1.el7.x86_64
> System Specifications: [32 vCPU, 250GB]
>
> Br,
> Veerendra Pulapa | Technical Consultant
> M: +91-9949349894 | www.ashnik.com
>
>
> <https://www.linkedin.com/company/ashnik-pte-ltd/;
> <https://www.facebook.com/AshnikBiz;
> <https://www.youtube.com/user/ashnikbiz;
> <https://www.instagram.com/ashnikbiz/; <https://twitter.com/Ashnikbiz;
>
>
> *
> ______________________________________________________________________________________
> This email may contain confidential, privileged or copyright material and
> is solely for the use of the intended recipient(s). If you are not the
> rightful recipient of this email, please delete this email immediately and
> inform the recipient. *
>
> --
> Achilleas Mantzios
> IT DEV - HEAD
> IT DEPT
> Dynacom Tankers Mgmt (as agents only)
>
>
--
*________________________________________________________________________________________
*_This email may contain confidential, privileged or copyright material and
is solely for the use of the intended recipient(s). If you are not the
rightful recipient of this email, please delete this email immediately and
inform the recipient.
_
*
*
^ permalink raw reply [nested|flat] 16+ messages in thread
* Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
@ 2024-06-17 14:39 Laurenz Albe <laurenz.albe@cybertec.at>
parent: Veerendra Pulapa <veerendra.pulapa@ashnik.com>
0 siblings, 1 reply; 16+ messages in thread
From: Laurenz Albe @ 2024-06-17 14:39 UTC (permalink / raw)
To: Veerendra Pulapa <veerendra.pulapa@ashnik.com>; Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>; +Cc: pgsql-admin@lists.postgresql.org
On Mon, 2024-06-17 at 18:30 +0530, Veerendra Pulapa wrote:
> LOG: startup process (PID 21704) was terminated by signal 11: Segmentation fault
If you want any support for that, you need to collect a core dump and
generate a stack trace. Make sure that you have the debugging symbols installed.
Also, we'd need to see the log messages *before* the lines you show. Everything
since the start of the server.
A segmentation fault is caused by a software bug. Since it happens during
recovery, perhaps the WAL that is being replayed is corrupted and makes
PostgreSQL fail.
My recommendation is to restore your last good backup.
Yours,
Laurenz Albe
^ permalink raw reply [nested|flat] 16+ messages in thread
* Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
@ 2024-06-19 07:27 Veerendra Pulapa <veerendra.pulapa@ashnik.com>
parent: Laurenz Albe <laurenz.albe@cybertec.at>
0 siblings, 1 reply; 16+ messages in thread
From: Veerendra Pulapa @ 2024-06-19 07:27 UTC (permalink / raw)
To: Laurenz Albe <laurenz.albe@cybertec.at>; pgsql-admin; +Cc: Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>; pgsql-admin@lists.postgresql.org
Dear,
I have run coredump in my current system but I want to understand the
coredump file and what went wrong with the signal 11 error(segmentation
fault)?
below are the coredump output:
/usr/bin/gdb /usr/pgsql-13/bin/postgres
/mnt/spool/abrt/ccpp-2024-06-18-11\:05\:00-7214/coredump
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-120.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/;...
Reading symbols from /usr/pgsql-13/bin/postgres...Reading symbols from
/usr/lib/debug/usr/pgsql-13/bin/postgres.debug...done.
done.
warning: core file may not match specified executable file.
[New LWP 7214]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `postgres: startup recovering
0000000100007C49000000A5'.
Program terminated with signal 11, Segmentation fault.
#0 0x00000000004ddc75 in _bt_swap_posting (newitem=newitem@entry=0x254bee8,
oposting=oposting@entry=0x7fc6c1b3ee20, postingoff=1) at nbtdedup.c:800
800 nbtdedup.c: No such file or directory.
Missing separate debuginfos, use: debuginfo-install
audit-libs-2.8.5-4.el7.x86_64 bzip2-libs-1.0.6-13.el7.x86_64
cyrus-sasl-lib-2.1.26-24.el7_9.x86_64 elfutils-libelf-0.176-5.el7.x86_64
elfutils-libs-0.176-5.el7.x86_64 glibc-2.17-326.el7_9.x86_64
keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-55.el7_9.x86_64
libattr-2.4.46-13.el7.x86_64 libcap-2.22-11.el7.x86_64
libcap-ng-0.7.5-4.el7.x86_64 libcom_err-1.42.9-19.el7.x86_64
libgcc-4.8.5-44.el7.x86_64 libgcrypt-1.5.3-14.el7.x86_64
libgpg-error-1.12-3.el7.x86_64 libicu-50.2-4.el7_7.x86_64
libselinux-2.5-15.el7.x86_64 libstdc++-4.8.5-44.el7.x86_64
libxml2-2.9.1-6.el7_9.6.x86_64 lz4-1.8.3-1.el7.x86_64
nspr-4.35.0-1.el7_9.x86_64 nss-3.90.0-2.el7_9.x86_64
nss-softokn-freebl-3.90.0-6.el7_9.x86_64 nss-util-3.90.0-1.el7_9.x86_64
openldap-2.4.44-25.el7_9.x86_64 openssl-libs-1.0.2k-26.el7_9.x86_64
pam-1.1.8-23.el7.x86_64 pcre-8.32-17.el7.x86_64
systemd-libs-219-78.el7_9.9.x86_64 xz-libs-5.2.2-2.el7_9.x86_64
zlib-1.2.7-21.el7_9.x86_64
(gdb) bt
#0 0x00000000004ddc75 in _bt_swap_posting (newitem=newitem@entry=0x254bee8,
oposting=oposting@entry=0x7fc6c1b3ee20, postingoff=1) at nbtdedup.c:800
#1 0x00000000004ee423 in btree_xlog_insert (isleaf=isleaf@entry=true,
ismeta=ismeta@entry=false, posting=posting@entry=true,
record=record@entry=0x2529d48)
at nbtxlog.c:224
#2 0x00000000004eeea4 in btree_redo (record=0x2529d48) at nbtxlog.c:969
#3 0x000000000051caa5 in StartupXLOG () at xlog.c:7319
#4 0x00000000007197a1 in StartupProcessMain () at startup.c:204
#5 0x000000000052b94c in AuxiliaryProcessMain (argc=argc@entry=2,
argv=argv@entry=0x7ffd95f45740) at bootstrap.c:443
#6 0x000000000071679e in StartChildProcess (type=StartupProcess) at
postmaster.c:5492
#7 0x00000000007190e4 in PostmasterMain (argc=argc@entry=3,
argv=argv@entry=0x24f9280)
at postmaster.c:1404
#8 0x0000000000488bbd in main (argc=3, argv=0x24f9280) at main.c:210
(gdb)
Br,
Veerendra Pulapa | Technical Consultant
M: +91-9949349894 | www.ashnik.com
<https://www.linkedin.com/company/ashnik-pte-ltd/;
<https://www.facebook.com/AshnikBiz;
<https://www.youtube.com/user/ashnikbiz;
<https://www.instagram.com/ashnikbiz/; <https://twitter.com/Ashnikbiz;
On Mon, Jun 17, 2024 at 8:09 PM Laurenz Albe <laurenz.albe@cybertec.at>
wrote:
> On Mon, 2024-06-17 at 18:30 +0530, Veerendra Pulapa wrote:
> > LOG: startup process (PID 21704) was terminated by signal 11:
> Segmentation fault
>
> If you want any support for that, you need to collect a core dump and
> generate a stack trace. Make sure that you have the debugging symbols
> installed.
>
> Also, we'd need to see the log messages *before* the lines you show.
> Everything
> since the start of the server.
>
> A segmentation fault is caused by a software bug. Since it happens during
> recovery, perhaps the WAL that is being replayed is corrupted and makes
> PostgreSQL fail.
>
> My recommendation is to restore your last good backup.
>
> Yours,
> Laurenz Albe
>
--
*________________________________________________________________________________________
*_This email may contain confidential, privileged or copyright material and
is solely for the use of the intended recipient(s). If you are not the
rightful recipient of this email, please delete this email immediately and
inform the recipient.
_
*
*
^ permalink raw reply [nested|flat] 16+ messages in thread
* Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
@ 2024-06-19 07:50 Laurenz Albe <laurenz.albe@cybertec.at>
parent: Veerendra Pulapa <veerendra.pulapa@ashnik.com>
0 siblings, 1 reply; 16+ messages in thread
From: Laurenz Albe @ 2024-06-19 07:50 UTC (permalink / raw)
To: Veerendra Pulapa <veerendra.pulapa@ashnik.com>; pgsql-admin; +Cc: Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>; pgsql-admin@lists.postgresql.org
On Wed, 2024-06-19 at 12:57 +0530, Veerendra Pulapa wrote:
> Dear,
>
> I have run coredump in my current system but I want to understand the coredump
> file and what went wrong with the signal 11 error(segmentation fault)?
>
> below are the coredump output:
>
> Program terminated with signal 11, Segmentation fault.
> #0 0x00000000004ddc75 in _bt_swap_posting (newitem=newitem@entry=0x254bee8, oposting=oposting@entry=0x7fc6c1b3ee20, postingoff=1) at nbtdedup.c:800
That is revealing. Line number 800 has been a comment since version 13.4,
so you must be running 13.3 or lower.
The only commit that happened to the file between 13.3 and 13.4 is fa675af59f,
which added a check to defend against a crash in connection with corrupted indexes.
So I suggest that you update to 13.latest, as you should always do.
See if the crash turns into an error message.
Then you should try to rebuild the index with REINDEX. See if that gets rid
of the problem.
However, your server log suggests that you hit the crash while in crash recovery.
In that case you won't get far enough to rebuild any indexes.
Your options are probably to restore a backup or to venture "pg_resetwal" to
get the system up. But "pg_resetwal" will destroy data and further corrupt
your database, so take a backup before you do that.
The goal of "pg_resetwal" is to get the server up so you can try to "pg_dump"
the database and restore it somewhere else.
Yours,
Laurenz Albe
^ permalink raw reply [nested|flat] 16+ messages in thread
* Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
@ 2024-06-19 08:02 Veerendra Pulapa <veerendra.pulapa@ashnik.com>
parent: Laurenz Albe <laurenz.albe@cybertec.at>
0 siblings, 1 reply; 16+ messages in thread
From: Veerendra Pulapa @ 2024-06-19 08:02 UTC (permalink / raw)
To: Laurenz Albe <laurenz.albe@cybertec.at>; +Cc: pgsql-admin; Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>; pgsql-admin@lists.postgresql.org
How do we check code 13.3 and 13.4 nbtdedup.c:800?
Regarding this issue can we get any relevant information? Where can we find
bug information?
Br,
Veerendra Pulapa | Technical Consultant
M: +91-9949349894 | www.ashnik.com
<https://www.linkedin.com/company/ashnik-pte-ltd/;
<https://www.facebook.com/AshnikBiz;
<https://www.youtube.com/user/ashnikbiz;
<https://www.instagram.com/ashnikbiz/; <https://twitter.com/Ashnikbiz;
On Wed, Jun 19, 2024 at 1:20 PM Laurenz Albe <laurenz.albe@cybertec.at>
wrote:
> On Wed, 2024-06-19 at 12:57 +0530, Veerendra Pulapa wrote:
> > Dear,
> >
> > I have run coredump in my current system but I want to understand the
> coredump
> > file and what went wrong with the signal 11 error(segmentation fault)?
> >
> > below are the coredump output:
> >
> > Program terminated with signal 11, Segmentation fault.
> > #0 0x00000000004ddc75 in _bt_swap_posting (newitem=newitem@entry=0x254bee8,
> oposting=oposting@entry=0x7fc6c1b3ee20, postingoff=1) at nbtdedup.c:800
>
> That is revealing. Line number 800 has been a comment since version 13.4,
> so you must be running 13.3 or lower.
>
> The only commit that happened to the file between 13.3 and 13.4 is
> fa675af59f,
> which added a check to defend against a crash in connection with corrupted
> indexes.
>
> So I suggest that you update to 13.latest, as you should always do.
> See if the crash turns into an error message.
>
> Then you should try to rebuild the index with REINDEX. See if that gets
> rid
> of the problem.
>
> However, your server log suggests that you hit the crash while in crash
> recovery.
> In that case you won't get far enough to rebuild any indexes.
>
> Your options are probably to restore a backup or to venture "pg_resetwal"
> to
> get the system up. But "pg_resetwal" will destroy data and further corrupt
> your database, so take a backup before you do that.
> The goal of "pg_resetwal" is to get the server up so you can try to
> "pg_dump"
> the database and restore it somewhere else.
>
> Yours,
> Laurenz Albe
>
--
*________________________________________________________________________________________
*_This email may contain confidential, privileged or copyright material and
is solely for the use of the intended recipient(s). If you are not the
rightful recipient of this email, please delete this email immediately and
inform the recipient.
_
*
*
^ permalink raw reply [nested|flat] 16+ messages in thread
* Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
@ 2024-06-19 08:08 Laurenz Albe <laurenz.albe@cybertec.at>
parent: Veerendra Pulapa <veerendra.pulapa@ashnik.com>
0 siblings, 1 reply; 16+ messages in thread
From: Laurenz Albe @ 2024-06-19 08:08 UTC (permalink / raw)
To: Veerendra Pulapa <veerendra.pulapa@ashnik.com>; +Cc: pgsql-admin; Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>; pgsql-admin@lists.postgresql.org
On Wed, 2024-06-19 at 13:32 +0530, Veerendra Pulapa wrote:
> How do we check code 13.3 and 13.4 nbtdedup.c:800?
>
> Regarding this issue can we get any relevant information? Where can we find bug information?
Huh? PostgreSQL is open source.
I told you it is commit fa675af59f, so you can look at
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=fa675af59f
It is also listed in the release notes of 13.4:
https://www.postgresql.org/docs/13/release-13-4.html
- Harden B-tree posting list split code against corrupt data (Peter Geoghegan)
Throw an error, rather than crashing, for an attempt to insert an item with a
TID identical to an existing entry. While that shouldn't ever happen, it has
been reported to happen when the index is inconsistent with its table.
Yours,
Laurenz Albe
^ permalink raw reply [nested|flat] 16+ messages in thread
* Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
@ 2024-06-19 08:12 Michael Banck <mbanck@gmx.net>
parent: Laurenz Albe <laurenz.albe@cybertec.at>
0 siblings, 1 reply; 16+ messages in thread
From: Michael Banck @ 2024-06-19 08:12 UTC (permalink / raw)
To: Veerendra Pulapa <veerendra.pulapa@ashnik.com>; +Cc: Laurenz Albe <laurenz.albe@cybertec.at>; pgsql-admin; Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>; pgsql-admin@lists.postgresql.org
Hi,
On Wed, Jun 19, 2024 at 10:08:14AM +0200, Laurenz Albe wrote:
> On Wed, 2024-06-19 at 13:32 +0530, Veerendra Pulapa wrote:
> > How do we check code 13.3 and 13.4 nbtdedup.c:800?
> >
> > Regarding this issue can we get any relevant information? Where can we find bug information?
>
> Huh? PostgreSQL is open source.
>
> I told you it is commit fa675af59f, so you can look at
>
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=fa675af59f
>
> It is also listed in the release notes of 13.4:
> https://www.postgresql.org/docs/13/release-13-4.html
>
> - Harden B-tree posting list split code against corrupt data (Peter Geoghegan)
>
> Throw an error, rather than crashing, for an attempt to insert an item with a
> TID identical to an existing entry. While that shouldn't ever happen, it has
> been reported to happen when the index is inconsistent with its table.
Right, and the reason why the index is inconsistent with its table is
probably due to the ill-fated OS update you mentioned; if that was
in-place and unless you REINDEXed all the text-column-based indexes,
this might have lead to index corruption, so REINDEX your database after
you upgraded to the latest minor release of version 13.
Michael
^ permalink raw reply [nested|flat] 16+ messages in thread
* Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
@ 2024-06-22 06:38 Veerendra Pulapa <veerendra.pulapa@ashnik.com>
parent: Michael Banck <mbanck@gmx.net>
0 siblings, 1 reply; 16+ messages in thread
From: Veerendra Pulapa @ 2024-06-22 06:38 UTC (permalink / raw)
To: Michael Banck <mbanck@gmx.net>; pgsql-admin; +Cc: Laurenz Albe <laurenz.albe@cybertec.at>; Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>; pgsql-admin@lists.postgresql.org
Hi All,
Is there any way to reproduce the issue on different OS and Different DB
versions?
Br,
Veerendra Pulapa | Technical Consultant
M: +91-9949349894 | www.ashnik.com
<https://www.linkedin.com/company/ashnik-pte-ltd/;
<https://www.facebook.com/AshnikBiz;
<https://www.youtube.com/user/ashnikbiz;
<https://www.instagram.com/ashnikbiz/; <https://twitter.com/Ashnikbiz;
On Wed, Jun 19, 2024 at 1:42 PM Michael Banck <mbanck@gmx.net> wrote:
> Hi,
>
> On Wed, Jun 19, 2024 at 10:08:14AM +0200, Laurenz Albe wrote:
> > On Wed, 2024-06-19 at 13:32 +0530, Veerendra Pulapa wrote:
> > > How do we check code 13.3 and 13.4 nbtdedup.c:800?
> > >
> > > Regarding this issue can we get any relevant information? Where can we
> find bug information?
> >
> > Huh? PostgreSQL is open source.
> >
> > I told you it is commit fa675af59f, so you can look at
> >
> >
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=fa675af59f
> >
> > It is also listed in the release notes of 13.4:
> > https://www.postgresql.org/docs/13/release-13-4.html
> >
> > - Harden B-tree posting list split code against corrupt data (Peter
> Geoghegan)
> >
> > Throw an error, rather than crashing, for an attempt to insert an item
> with a
> > TID identical to an existing entry. While that shouldn't ever happen,
> it has
> > been reported to happen when the index is inconsistent with its table.
>
> Right, and the reason why the index is inconsistent with its table is
> probably due to the ill-fated OS update you mentioned; if that was
> in-place and unless you REINDEXed all the text-column-based indexes,
> this might have lead to index corruption, so REINDEX your database after
> you upgraded to the latest minor release of version 13.
>
>
> Michael
>
--
*________________________________________________________________________________________
*_This email may contain confidential, privileged or copyright material and
is solely for the use of the intended recipient(s). If you are not the
rightful recipient of this email, please delete this email immediately and
inform the recipient.
_
*
*
^ permalink raw reply [nested|flat] 16+ messages in thread
* Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
@ 2024-07-01 12:26 Veerendra Pulapa <veerendra.pulapa@ashnik.com>
parent: Veerendra Pulapa <veerendra.pulapa@ashnik.com>
0 siblings, 0 replies; 16+ messages in thread
From: Veerendra Pulapa @ 2024-07-01 12:26 UTC (permalink / raw)
To: Muhammad Waqas <waqas.m@bitnine.net>; pgsql-admin; Pgsql-admin <pgsql-admin@lists.postgresql.org>; Michael Banck <mbanck@gmx.net>; Laurenz Albe <laurenz.albe@cybertec.at>; Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>; Vijaykumar Jain <vijaykumarjain.github@gmail.com>; lennam@incisivetechgroup.com
Dear All,
I hope this message finds you well.
I am reaching out to discuss an issue we recently encountered with our
PostgreSQL setup, where a bug triggered on our standby servers before it
affected the master. I am seeking insights into whether the resource
differences between our servers could have played a role in this sequence
of events.
*Issue Overview:*
- We observed a signal 11 (segmentation fault) error that first appeared
on our standby servers and subsequently affected the master server.
- Our setup consists of a master server with higher resources and
multiple standby servers with relatively lower resources.
*Concerns:*
- The standby servers have fewer resources compared to the master, which
may have contributed to the bug being triggered on them first?
- We are considering whether the disparity in resources could lead to
performance bottlenecks or stability issues, causing the standby servers to
encounter the bug earlier than the master?
*Request for Insights:*
- Has anyone else experienced similar issues where bugs or faults are
observed on standby servers before the master?
- Could the resource differences between the master and standby servers
play a significant role in this behavior?
- Are there best practices for ensuring stability across servers with
different resource allocations, especially in a High Availability (HA)
setup?
I would greatly appreciate any insights, experiences, or suggestions you
might have regarding this issue. Understanding the underlying reasons will
help us optimize our setup and prevent future occurrences.
Thank you for your time and expertise.
Br,
Veerendra Pulapa | Technical Consultant
M: +91-9949349894 | www.ashnik.com
<https://www.linkedin.com/company/ashnik-pte-ltd/;
<https://www.facebook.com/AshnikBiz;
<https://www.youtube.com/user/ashnikbiz;
<https://www.instagram.com/ashnikbiz/; <https://twitter.com/Ashnikbiz;
On Mon, Jun 24, 2024 at 10:10 AM Muhammad Waqas <waqas.m@bitnine.net> wrote:
> yes you can
>
> 2024년 6월 22일 (토) 오전 11:38, Veerendra Pulapa <veerendra.pulapa@ashnik.com>님이
> 작성:
>
>> Hi All,
>>
>> Is there any way to reproduce the issue on different OS and Different DB
>> versions?
>>
>> Br,
>> Veerendra Pulapa | Technical Consultant
>> M: +91-9949349894 | www.ashnik.com
>>
>>
>> <https://www.linkedin.com/company/ashnik-pte-ltd/;
>> <https://www.facebook.com/AshnikBiz;
>> <https://www.youtube.com/user/ashnikbiz;
>> <https://www.instagram.com/ashnikbiz/; <https://twitter.com/Ashnikbiz;
>>
>>
>> On Wed, Jun 19, 2024 at 1:42 PM Michael Banck <mbanck@gmx.net> wrote:
>>
>>> Hi,
>>>
>>> On Wed, Jun 19, 2024 at 10:08:14AM +0200, Laurenz Albe wrote:
>>> > On Wed, 2024-06-19 at 13:32 +0530, Veerendra Pulapa wrote:
>>> > > How do we check code 13.3 and 13.4 nbtdedup.c:800?
>>> > >
>>> > > Regarding this issue can we get any relevant information? Where can
>>> we find bug information?
>>> >
>>> > Huh? PostgreSQL is open source.
>>> >
>>> > I told you it is commit fa675af59f, so you can look at
>>> >
>>> >
>>> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=fa675af59f
>>> >
>>> > It is also listed in the release notes of 13.4:
>>> > https://www.postgresql.org/docs/13/release-13-4.html
>>> >
>>> > - Harden B-tree posting list split code against corrupt data (Peter
>>> Geoghegan)
>>> >
>>> > Throw an error, rather than crashing, for an attempt to insert an
>>> item with a
>>> > TID identical to an existing entry. While that shouldn't ever
>>> happen, it has
>>> > been reported to happen when the index is inconsistent with its
>>> table.
>>>
>>> Right, and the reason why the index is inconsistent with its table is
>>> probably due to the ill-fated OS update you mentioned; if that was
>>> in-place and unless you REINDEXed all the text-column-based indexes,
>>> this might have lead to index corruption, so REINDEX your database after
>>> you upgraded to the latest minor release of version 13.
>>>
>>>
>>> Michael
>>>
>>
>>
>> *______________________________________________________________________________________This
>> email may contain confidential, privileged or copyright material and is
>> solely for the use of the intended recipient(s). If you are not the
>> rightful recipient of this email, please delete this email immediately and
>> inform the recipient. *
>>
>>
--
*________________________________________________________________________________________
*_This email may contain confidential, privileged or copyright material and
is solely for the use of the intended recipient(s). If you are not the
rightful recipient of this email, please delete this email immediately and
inform the recipient.
_
*
*
^ permalink raw reply [nested|flat] 16+ messages in thread
* Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
@ 2024-07-01 12:40 Laurenz Albe <laurenz.albe@cybertec.at>
0 siblings, 0 replies; 16+ messages in thread
From: Laurenz Albe @ 2024-07-01 12:40 UTC (permalink / raw)
To: veerendra.pulapa@ashnik.com; pgsql-admin
Veerendra Pulapa wrote:
> I am reaching out to discuss an issue we recently encountered with our PostgreSQL
> setup, where a bug triggered on our standby servers before it affected the master.
> I am seeking insights into whether the resource differences between our servers
> could have played a role in this sequence of events.
>
> Issue Overview:
>
> We observed a signal 11 (segmentation fault) error that first appeared on our
> standby servers and subsequently affected the master server.
Please don't hijack another thread, start your own.
You should tell us the exact PostgreSQL version and operating system.
Also, tell us exactly what you did to trigger the problem.
Collect a core dump and get a stack trace (you need debugging symbols):
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
Yours,
Laurenz Albe
^ permalink raw reply [nested|flat] 16+ messages in thread
end of thread, other threads:[~2024-07-01 12:40 UTC | newest]
Thread overview: 16+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-06-16 23:49 Urgent: Segmentation Fault in PostgreSQL postmaster Process Veerendra Pulapa <veerendra.pulapa@ashnik.com>
2024-06-17 03:02 ` lennam@incisivetechgroup.com
2024-06-17 12:54 ` Veerendra Pulapa <veerendra.pulapa@ashnik.com>
2024-06-17 05:10 ` Vijaykumar Jain <vijaykumarjain.github@gmail.com>
2024-06-17 12:55 ` Veerendra Pulapa <veerendra.pulapa@ashnik.com>
2024-06-17 05:14 ` Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>
2024-06-17 13:00 ` Veerendra Pulapa <veerendra.pulapa@ashnik.com>
2024-06-17 14:39 ` Laurenz Albe <laurenz.albe@cybertec.at>
2024-06-19 07:27 ` Veerendra Pulapa <veerendra.pulapa@ashnik.com>
2024-06-19 07:50 ` Laurenz Albe <laurenz.albe@cybertec.at>
2024-06-19 08:02 ` Veerendra Pulapa <veerendra.pulapa@ashnik.com>
2024-06-19 08:08 ` Laurenz Albe <laurenz.albe@cybertec.at>
2024-06-19 08:12 ` Michael Banck <mbanck@gmx.net>
2024-06-22 06:38 ` Veerendra Pulapa <veerendra.pulapa@ashnik.com>
2024-07-01 12:26 ` Veerendra Pulapa <veerendra.pulapa@ashnik.com>
2024-07-01 12:40 Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process Laurenz Albe <laurenz.albe@cybertec.at>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox