Re: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Andres Freund <andres@anarazel.de>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, Yuli Khodorkovskiy <yuli.khodorkovskiy@crunchydata.com>, pgsql-bugs@lists.postgresql.org
Date: 2019-05-18T09:35:22Z
Lists: pgsql-bugs
On Fri, May 17, 2019 at 01:24:43PM -0700, Andres Freund wrote:
> I don't think a windows-only patch is the same thing as a feature, one
> that makes debugging easier to boot, that's applicable to all
> platforms.
We are discussing here a set of problems which breaks the logging
collector to work on Windows, requiring mostly a Windows patch. And I
am not much willing to mess up with the area of shared memory handling
on Windows a couple of days before a beta.
>> diff --git a/src/tools/msvc/config_default.pl b/src/tools/msvc/config_default.pl
>> @@ -17,7 +17,7 @@ our $config = {
>> gss => undef, # --with-gssapi=<path>
>> icu => undef, # --with-icu=<path>
>> nls => undef, # --enable-nls=<path>
>> - tap_tests => undef, # --enable-tap-tests
>> + tap_tests => 1, # --enable-tap-tests
>> tcl => undef, # --with-tcl=<path>
>> perl => undef, # --with-perl
>> python => undef, # --with-python=<path>
>
> Hm? Is this to coerce cfbot?
This is part of the patch only because it has proved to be useful for
testing with MSVC on my VMs. I am not suggesting to add that in this
patch if this gets merged into HEAD. It is actually a good idea to
enforce that sometimes for the cfbot.. I'll remember your suggestion
for future patches.
--
Michael
Commits
-
Rearrange postmaster's startup sequence for better syslogger results.
- 9a86f03b4e8c 13.0 landed
-
Improve logrotate test so that it meaningfully exercises syslogger.
- 9d5c22d28f8c 12.0 landed
-
Revert "postmaster: Start syslogger earlier".
- 833451552925 12.0 landed
-
postmaster: Start syslogger earlier
- 57431a911d3a 12.0 cited