Re: BF assertion failure on mandrill in walsender, v13

From: Noah Misch <noah(at)leadboat(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: BF assertion failure on mandrill in walsender, v13
Date: 2021-06-11 01:39:42
Message-ID: 20210611013942.GA558096@rfd.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 10, 2021 at 09:08:06AM -0400, Andrew Dunstan wrote:
> On 6/10/21 1:47 AM, Noah Misch wrote:
> > On Thu, Jun 10, 2021 at 10:47:20AM +1200, Thomas Munro wrote:
> >> Not sure if there is much chance of debugging this one-off failure in
> >> without a backtrace (long shot: any chance there's still a core
> >> file?)
> > No; it was probably in a directory deleted for each run. One would need to
> > add dbx support to the buildfarm client, or perhaps add support for saving
> > build directories when there's a core, so I can operate dbx manually.
>
> This is what the setting "keep_error_builds" does. In the END handler it
> renames the build and install directories with a timestamp. Cleanup is
> left to the user.

Great. The machine has ample disk, so I'll add that setting.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2021-06-11 01:40:36 Re: Race condition in recovery?
Previous Message Kyotaro Horiguchi 2021-06-11 01:37:47 Re: Logical replication keepalive flood