From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | pgdba pgdba <postgresdba12(at)outlook(dot)com> |
Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Pgbackrest Restore Error - Segmentation fault (core dumped) |
Date: | 2023-09-06 12:15:48 |
Message-ID: | 485D5DB0-F5FE-4197-94ED-627F162F80DF@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On 6 Sep 2023, at 13:08, pgdba pgdba <postgresdba12(at)outlook(dot)com> wrote:
>
> Hello, when I restore with Pgbackrest, I get the following error, I couldn't find a solution when I researched, can you support?
You might be better off raising this question on the pgbackreset Github repo as
an issue, where more pgbackrest developers are likely to see it.
Are you able to repeat the issue such that you can get a stack trace from it?
That will be helpful for anyone trying to find the issue. The postgres wiki
has some information on getting a stack trace from a postgres process, and
while not the same the process is similar enough that it might be helpful
reading.
--
Daniel Gustafsson
From | Date | Subject | |
---|---|---|---|
Next Message | Rob Sargent | 2023-09-06 13:32:49 | Re: Pgbackrest Restore Error - Segmentation fault (core dumped) |
Previous Message | Chris Travers | 2023-09-06 11:10:33 | Re: Postgres partition max limit |