From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: yuli.khodorkovskiy@crunchydata.com
Subject: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND
Date: Tue, 14 May 2019 18:28:44 +0000
Message-ID: <15804-3721117bf40fb654@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 15804
Logged by: Yulian Khodorkovskiy
Email address: yuli.khodorkovskiy@crunchydata.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, yuli.khodorkovskiy@crunchydata.com
Subject: Re: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND
In-Reply-To: <15804-3721117bf40fb654@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox