| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Arne Roland <A(dot)Roland(at)index(dot)de> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: dsa_allocate() faliure |
| Date: | 2019-02-04 21:47:08 |
| Message-ID: | 20190204214708.GI29720@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2019-02-04 22:02:22 | Re: Pre-v11 appearances of the word "procedure" in v11 docs |
| Previous Message | Bossart, Nathan | 2019-02-04 21:22:38 | Re: New vacuum option to do only freezing |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2019-02-05 20:30:36 | Re: How can sort performance be so different |
| Previous Message | Arne Roland | 2019-02-04 20:31:47 | RE: dsa_allocate() faliure |