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 20:39:09
Message-ID: CA+hUKGKiTd9fB2s51ZaJV016N_sWvoULtYCmKdp9DzGYARB7jQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Apr 2, 2019 at 12:52 AM Christian Ullrich <chris(at)chrullrich(dot)net> 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Rahila Syed 2019-04-01 20:43:53 Re: monitoring CREATE INDEX [CONCURRENTLY]
Previous Message Thomas Munro 2019-04-01 20:37:06 Re: pgsql: Compute XID horizon for page level index vacuum on primary.