| From: | Christian Ullrich <chris(at)chrullrich(dot)net> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: C_C_A animal on HEAD gets stuck in initdb |
| Date: | 2019-04-01 11:52:09 |
| Message-ID: | 7482ac53-0b57-a06a-7a91-1801a990a107@chrullrich.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Christian Ullrich wrote:
> * Thomas Munro wrote:
>
>> On Mon, Apr 1, 2019 at 9:39 PM Christian Ullrich
>> <chris(at)chrullrich(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 2019-04-01 12:14:56 | Re: SQL statement PREPARE does not work in ECPG |
| Previous Message | Christian Ullrich | 2019-04-01 11:31:23 | Re: C_C_A animal on HEAD gets stuck in initdb |