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

From Justin Pryzby
Subject Re: dsa_allocate() faliure
Date
Msg-id 20190210160035.GS31721@telsasoft.com
Whole thread Raw
In response to Re: dsa_allocate() faliure  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: dsa_allocate() faliure  (Sergei Kornilov <sk@zsrv.org>)
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Fixing findDependentObjects()'s dependency on scan order(regressions in DROP diagnostic messages)
Next
From: Sergei Kornilov
Date:
Subject: Re: dsa_allocate() faliure