Re: C_C_A animal on HEAD gets stuck in initdb

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Christian Ullrich <chris(at)chrullrich(dot)net>
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 09:26:30
Message-ID: CA+hUKGJ2bikBHnNxAH5F0Dy3SKUH7nxR7aCiy+R+zzrrp+umcw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

--
Thomas Munro
https://enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Matsumura, Ryo 2019-04-01 09:29:06 RE: SQL statement PREPARE does not work in ECPG
Previous Message Peter Eisentraut 2019-04-01 09:25:46 Re: Why does ExecComputeStoredGenerated() form a heap tuple