Re: C_C_A animal on HEAD gets stuck in initdb - Mailing list pgsql-hackers

From Christian Ullrich
Subject Re: C_C_A animal on HEAD gets stuck in initdb
Date
Msg-id 7482ac53-0b57-a06a-7a91-1801a990a107@chrullrich.net
Whole thread Raw
In response to Re: C_C_A animal on HEAD gets stuck in initdb  (Christian Ullrich <chris@chrullrich.net>)
Responses Re: C_C_A animal on HEAD gets stuck in initdb
List pgsql-hackers
* Christian Ullrich wrote:

> * Thomas Munro wrote:
> 
>> On Mon, Apr 1, 2019 at 9:39 PM Christian Ullrich 
>> <chris@chrullrich.net> wrote:

>>> my CLOBBER_CACHE_ALWAYS animal, jaguarundi, has gotten stuck in "make
>>> check"'s initdb three times in a row now.
>>
>> Could it be the same as this?
>>
>> https://www.postgresql.org/message-id/CA%2BhUKGLCwPF0S4Mk7S8qw%2BDK0Bq65LueN9rofAA3HHSYikW-Zw%40mail.gmail.com 
>>
>>
>> I see that its first failure was after commit 558a9165e0 (along with 
>> others).
> 
> It does look very similar. I don't have a working gdb on the box, hence 
> this is from lldb.

I think the patch in the linked message works; it doesn't get stuck 
anymore. It's still slow as molasses with C_C_A; this animal can take 
12+ hours to complete.

-- 
Christian

pgsql-hackers by date:

Previous
From: Christian Ullrich
Date:
Subject: Re: C_C_A animal on HEAD gets stuck in initdb
Next
From: Michael Meskes
Date:
Subject: Re: SQL statement PREPARE does not work in ECPG