Re: dsa_allocate() faliure

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Jakub Glapa <jakub(dot)glapa(at)gmail(dot)com>, Fabio Isabettini <fisabettini(at)voipfuture(dot)com>, Arne Roland <A(dot)Roland(at)index(dot)de>, Sand Stone <sand(dot)m(dot)stone(at)gmail(dot)com>, Rick Otten <rottenwindfish(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: dsa_allocate() faliure
Date: 2019-02-10 16:00:35
Message-ID: 20190210160035.GS31721@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

On Sun, Feb 10, 2019 at 12:10:52PM +0530, Robert Haas wrote:
> I think I see what's happening. At the moment the problem occurs,
> there is no btree - there is only a singleton range. So
> FreePageManagerInternal() takes the fpm->btree_depth == 0 branch and
> then ends up in the section with the comment /* Not contiguous; we
> need to initialize the btree. */. And that section, sadly, does not
> respect the 'soft' flag, so kaboom. Something like the attached might
> fix it.

I ran overnight with this patch, but all parallel processes ended up stuck in
the style of bug#15585. So that's either not the root cause, or there's a 2nd
issue.

https://www.postgresql.org/message-id/flat/15585-324ff6a93a18da46%40postgresql.org

Justin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sergei Kornilov 2019-02-10 16:11:22 Re: dsa_allocate() faliure
Previous Message Alvaro Herrera 2019-02-10 13:05:53 Re: Fixing findDependentObjects()'s dependency on scan order (regressions in DROP diagnostic messages)

Browse pgsql-performance by date

  From Date Subject
Next Message Sergei Kornilov 2019-02-10 16:11:22 Re: dsa_allocate() faliure
Previous Message Robert Haas 2019-02-10 06:40:52 Re: dsa_allocate() faliure