Re: dsa_allocate() faliure - Mailing list pgsql-performance

From Justin Pryzby
Subject Re: dsa_allocate() faliure
Date
Msg-id 20190204214708.GI29720@telsasoft.com
Whole thread Raw
In response to RE: dsa_allocate() faliure  (Arne Roland <A.Roland@index.de>)
List pgsql-performance
On Mon, Feb 04, 2019 at 08:31:47PM +0000, Arne Roland wrote:
> I could take a backup and restore the relevant tables on a throwaway system. You are just suggesting to replace line
728
> elog(FATAL,
>                                  "dsa_allocate could not find %zu free pages", npages);
> by
> elog(PANIC,
>                                  "dsa_allocate could not find %zu free pages", npages);
> correct? Just for my understanding: why would the shutdown of the whole instance create more helpful logging?

You'd also start with pg_ctl -c, which would allow it to dump core, which could
be inspected with GDB to show a backtrace and other internals, which up to now
nobody (including myself) has been able to provide.

Justin


pgsql-performance by date:

Previous
From: Arne Roland
Date:
Subject: RE: dsa_allocate() faliure
Next
From: Merlin Moncure
Date:
Subject: Re: How can sort performance be so different