Re: BF assertion failure on mandrill in walsender, v13

2021-06-10 Thread Noah Misch
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

Re: BF assertion failure on mandrill in walsender, v13

2021-06-10 Thread Andrew Dunstan
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

Re: BF assertion failure on mandrill in walsender, v13

2021-06-09 Thread Noah Misch
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

BF assertion failure on mandrill in walsender, v13

2021-06-09 Thread Thomas Munro
Hi, 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?), but for the record: mandrill choked on a null pointer passed to GetMemoryChunkContext() inside a walsender running logical replication. Possibly via