From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Cassandra Thrift <cssndrthrift(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump throwing segfault error during backup |
Date: | 2024-10-09 15:15:54 |
Message-ID: | a04878d9-c137-4791-a1a7-034776b893ba@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/7/24 22:42, 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
> Hat 4.8.5-39), 64-bit)
FYI, Postgres 12 goes EOL in one month.
What repo are you getting the Postgres package from, RH's or
community(PGDG).
If community see:
https://yum.postgresql.org/news/rhel7-end-of-life/
>
> We fond the timing which shows database backup is getting invoked at the
> time. So we had to stop backup (pg_backup)
I am not familiar with pg_backup, is that an actual program or our you
using it as alias for something else?
>
> we are manually taking table data currently.
Show the exact command/process you are using to do above.
>
> 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.
The most recent minor version of Postgres 12 is .20. It would not be a
bad idea to upgrade to that for immediate needs and then start testing
newer Postgres versions for a change in major version to get to a
version that will be community supported for some time.
>
> Regards
> Somraj Chakrabarty
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2024-10-09 15:24:38 | Re: Disk is filling up with large files. How can I clean? |
Previous Message | Laurenz Albe | 2024-10-09 14:51:16 | Re: Questions about document "Concurrenry control" section |