From: Justin Pryzby <pryzby@telsasoft.com>
To: Arne Roland <A.Roland@index.de>
Cc: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: dsa_allocate() faliure
Date: Mon, 4 Feb 2019 15:47:08 -0600
Message-ID: <20190204214708.GI29720@telsasoft.com> (raw)
In-Reply-To: <d9c6cc80e21241349db53b2f64075029@index.de>
References: <CAMAYy4+w3NTBM5JLWFi8twhWK4=k_5L4nV5+bYDSPu8r4b97Zg@mail.gmail.com>
<CAEepm=2aHnTfPJnPbeS3AxO-ENoUg5-akuD-7PWYbn8+-c9JmQ@mail.gmail.com>
<d9c6cc80e21241349db53b2f64075029@index.de>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pryzby@telsasoft.com, A.Roland@index.de, thomas.munro@enterprisedb.com, pgsql-performance@lists.postgresql.org
Subject: Re: dsa_allocate() faliure
In-Reply-To: <20190204214708.GI29720@telsasoft.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox