BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: yuli(dot)khodorkovskiy(at)crunchydata(dot)com
Subject: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND
Date: 2019-05-14 18:28:44
Message-ID: 15804-3721117bf40fb654@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Yuli Khodorkovskiy 2019-05-14 18:45:09 Re: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND
Previous Message Tom Lane 2019-05-14 15:29:31 Re: PostgreSQL 9.3.5 substring(text from pattern for escape) bug