On Tue, Apr 2, 2019 at 12:52 AM Christian Ullrich wrote:
> 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.
Thanks. I pushed the fix.
--
Thomas Munro
https://enterprisedb.com
On Mon, Apr 1, 2019 at 4:31 AM Christian Ullrich wrote:
> It does look very similar. I don't have a working gdb on the box, hence
> this is from lldb.
>
> (lldb) bt
I am almost certain that it's the same issue, based on this stack trace.
--
Peter Geoghegan
* Christian Ullrich wrote:
> * Thomas Munro wrote:
>
>> On Mon, Apr 1, 2019 at 9:39 PM Christian Ullrich
>> 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.postg
* Thomas Munro wrote:
> On Mon, Apr 1, 2019 at 9:39 PM Christian Ullrich 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%2BhUKGLCwPF0S4Mk7S
On Mon, Apr 1, 2019 at 9:39 PM Christian Ullrich 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%
Hello,
my CLOBBER_CACHE_ALWAYS animal, jaguarundi, has gotten stuck in "make
check"'s initdb three times in a row now.
I have trace output covering about the final minute of initdb. It mainly
consists of ~9 iterations of
- Open base/1/1259 [pg_class]
- Seek to end [twice]
- Open global/pg_
