Re: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND

From: Yuli Khodorkovskiy <yuli(dot)khodorkovskiy(at)crunchydata(dot)com>
To: Yuli Khodorkovskiy <yuli(dot)khodorkovskiy(at)crunchydata(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND
Date: 2019-05-14 18:45:09
Message-ID: 27CD45B5-88F7-4A09-8B31-EFE41FC37FE1@crunchydata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On May 14, 2019, at 2:28 PM, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 15804
> Logged by: Yulian Khodorkovskiy
> Email address: yuli(dot)khodorkovskiy(at)crunchydata(dot)com
> PostgreSQL version: Unsupported/Unknown
> Operating system: Centos 7.4
> Description:
>
> The following assertion fails when compiling postgres 12 on Linux (centos
> 7.4) with EXEC_BACKEND and logging_collector enabled:
>
> `Assert(UsedShmemSegAddr != NULL);` in `PGSharedMemoryNoReAttach()`
>
> Commit 57431a911d3a650451d198846ad3194900666152 appears to have introduced
> this regression by moving SysLogger_Start() before reset_shared() is called
> and shared memory is initialized.
>
> For what it's worth, Windows 10/jacana (and maybe other windows builds) on
> the build farm does not use logging_collector, which is perhaps why this
> regression was not caught.
>
> Yuli
>

Attached is a patch that fixes the issue in the bug report.

Attachment Content-Type Size
0001-Initialize-shared-memory-before-calling-SysLogger_St.patch application/octet-stream 1.6 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-05-14 19:52:04 Re: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND
Previous Message PG Bug reporting form 2019-05-14 18:28:44 BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND