Re: pgsql: Avoid "could not reattach" by providing space for concurrent all

From: Noah Misch <noah(at)leadboat(dot)com>
To: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Cc: pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Avoid "could not reattach" by providing space for concurrent all
Date: 2019-04-10 07:06:44
Message-ID: 20190410070644.GA2537154@rfd.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Tue, Apr 09, 2019 at 10:22:55AM -0400, Andrew Dunstan wrote:
> On Tue, Apr 9, 2019 at 12:44 AM Noah Misch <noah(at)leadboat(dot)com> wrote:
> >
> > Avoid "could not reattach" by providing space for concurrent allocation.
> >
>
> This has broken builds on frogmouth, and I'm betting any mingw animal.

Fixed in ba3fb5d.

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2019-04-10 09:49:37 pgsql: pg_restore: Make not verbose by default
Previous Message Masahiko Sawada 2019-04-10 07:05:34 Re: pgsql: Fix memory leak in pgbench