| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: BF assertion failure on mandrill in walsender, v13 |
| Date: | 2021-06-10 13:08:06 |
| Message-ID: | 482ba30e-d055-a14a-bae6-7987fee665a9@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
I don't have much knowledge of dbx, but I would take a patch for support.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anastasia Lubennikova | 2021-06-10 13:42:01 | Re: Testing autovacuum wraparound (including failsafe) |
| Previous Message | Bharath Rupireddy | 2021-06-10 13:06:50 | Re: Refactor "mutually exclusive options" error reporting code in parse_subscription_options |