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

From Sergei Kornilov
Subject Re: dsa_allocate() faliure
Date
Msg-id 14504121549815082@myt5-02b80404fd9e.qloud-c.yandex.net
Whole thread Raw
In response to Re: dsa_allocate() faliure  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: dsa_allocate() faliure  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-hackers
Hi

> 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.

Maybe i missed something in this discussion, but you can reproduce bug#15585? How? With this testcase:
https://www.postgresql.org/message-id/CAEepm%3D1MvOE-Sfv1chudx5KEmw_qHYrj8F9Og_WmdBRhXSQ%2B%2Bw%40mail.gmail.com?
 

regards, Sergei


pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: dsa_allocate() faliure
Next
From: Tom Lane
Date:
Subject: Re: Fixing findDependentObjects()'s dependency on scan order (regressions in DROP diagnostic messages)