pg.ddx.io pgsql-hackers@postgresql.org mailing list archive help / color / mirror / Atom feed From: Justin Pryzby <pryzby@telsasoft.com>
To: Andres Freund <andres@anarazel.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: pgsql-hackers@postgresql.org, Thomas Munro <thomas.munro@gmail.com>
Cc: Melanie Plageman <melanieplageman@gmail.com>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Daniel Gustafsson <daniel@yesql.se>
Subject: Re: ccache, MSVC, and meson
Date: Wed, 25 May 2022 22:26:12 -0500
Message-ID: <20220526032612.GW19626@telsasoft.com> (raw )
In-Reply-To: <20220525044817.kczou2nkbtk46itj@alap3.anarazel.de >
References: <20220522232606.GZ19626@telsasoft.com >
<20220524193059.n432rlzezckxr6x2@alap3.anarazel.de >
<20220524195202.GK19626@telsasoft.com >
<20220524203039.xyqjggtytsyizsbl@alap3.anarazel.de >
<20220524221747.GM19626@telsasoft.com >
<20220525044817.kczou2nkbtk46itj@alap3.anarazel.de >
On Tue, May 24, 2022 at 09:48:17PM -0700, Andres Freund wrote:
> > And when I pass /Oy- to "avoid omitting" frame pointers, several tests crash...
>
> Huh. Do you get a backtrace containing anything remotely meaningful?
They are interesting, but maybe not meaningful.
I tested a bunch of different optimization cases, this is just one. But the
other failures are similar.
https://cirrus-ci.com/task/5710595927310336
compiled with /Z7 /O1, test world fails in 15min (compared to ~18min without
/O1)
Child-SP RetAddr Call Site
000000b6`e27fed80 00007ffa`93b5b6ba pg_stat_statements!pg_stat_statements_reset_1_7+0x8a98
000000b6`e27fedb0 00007ffa`93b5a731 pg_stat_statements!pg_stat_statements_reset_1_7+0x8a5e
000000b6`e27fedf0 00007ffa`93b5a48c pg_stat_statements!pg_stat_statements_reset_1_7+0x7ad5
000000b6`e27feeb0 00007ffa`93b517b5 pg_stat_statements!pg_stat_statements_reset_1_7+0x7830
000000b6`e27feee0 00007ffa`93b52c6f pg_stat_statements!PG_init+0x7ad
000000b6`e27fef80 00007ff6`5544ebc3 pg_stat_statements!pg_stat_statements_reset_1_7+0x13
000000b6`e27fefb0 00007ff6`5546fa07 postgres!ExecEvalXmlExpr+0x9b3
000000b6`e27ff040 00007ff6`5530639c postgres!ExecReScanResult+0x1ef
000000b6`e27ff080 00007ff6`55306e91 postgres!ExecWithCheckOptions+0x4d0
000000b6`e27ff0c0 00007ffa`93b52f0c postgres!standard_ExecutorRun+0x13d
000000b6`e27ff140 00007ff6`550e636d pg_stat_statements!pg_stat_statements_reset_1_7+0x2b0
000000b6`e27ff2c0 00007ff6`550e5ba0 postgres!PortalRunFetch+0x645
000000b6`e27ff300 00007ff6`55013d31 postgres!PortalRun+0x24c
000000b6`e27ff4e0 00007ff6`55010db9 postgres!die+0x1cad
000000b6`e27ff5b0 00007ff6`5500e004 postgres!PostgresMain+0xb31
000000b6`e27ff7a0 00007ff6`55001592 postgres!SubPostmasterMain+0x230
000000b6`e27ff9d0 00007ff6`554c6ef0 postgres!main+0x2a2
000000b6`e27ffbc0 00007ffa`91217974 postgres!pg_check_dir+0x68c
000000b6`e27ffc00 00007ffa`9c84a2f1 KERNEL32!BaseThreadInitThunk+0x14
000000b6`e27ffc30 00000000`00000000 ntdll!RtlUserThreadStart+0x21
2022-05-23 09:05:28.893 GMT postmaster[6644] LOG: server process (PID 6388) was terminated by exception 0xC0000354
2022-05-23 09:05:28.893 GMT postmaster[6644] DETAIL: Failed process was running: SELECT pg_stat_statements_reset();
Child-SP RetAddr Call Site
0000004e`65ffbd40 00007ffa`93b66d3a basebackup_to_shell!PG_init+0x5c8c
0000004e`65ffbd70 00007ffa`93b67898 basebackup_to_shell!PG_init+0x5c52
0000004e`65ffbdb0 00007ffa`93b6817e basebackup_to_shell!PG_init+0x67b0
0000004e`65ffbe10 00007ffa`93b656bb basebackup_to_shell!PG_init+0x7096
0000004e`65ffbe40 00007ffa`93b65441 basebackup_to_shell!PG_init+0x45d3
0000004e`65ffbea0 00007ffa`93b653d2 basebackup_to_shell!PG_init+0x4359
0000004e`65ffbee0 00007ffa`93b6556e basebackup_to_shell!PG_init+0x42ea
0000004e`65ffbf10 00007ffa`93b657be basebackup_to_shell!PG_init+0x4486
0000004e`65ffbf90 00007ffa`93b616ce basebackup_to_shell!PG_init+0x46d6
0000004e`65ffc010 00007ffa`93b61041 basebackup_to_shell!PG_init+0x5e6
0000004e`65ffc040 00007ff6`5545be58 basebackup_to_shell+0x1041
0000004e`65ffc070 00007ff6`55289171 postgres!bbsink_zstd_new+0x100
0000004e`65ffc0b0 00007ff6`55288bd1 postgres!SendBaseBackup+0x2c8d
0000004e`65ffc160 00007ff6`55288b68 postgres!SendBaseBackup+0x26ed
0000004e`65ffce90 00007ff6`55288b68 postgres!SendBaseBackup+0x2684
0000004e`65ffdbc0 00007ff6`552878d1 postgres!SendBaseBackup+0x2684
0000004e`65ffe8f0 00007ff6`5528661f postgres!SendBaseBackup+0x13ed
0000004e`65fff110 00007ff6`550ad66c postgres!SendBaseBackup+0x13b
0000004e`65fff300 00007ff6`55010da9 postgres!exec_replication_command+0x3c0
0000004e`65fff340 00007ff6`5500e004 postgres!PostgresMain+0xb21
0000004e`65fff530 00007ff6`55001592 postgres!SubPostmasterMain+0x230
0000004e`65fff760 00007ff6`554c6ef0 postgres!main+0x2a2
0000004e`65fff950 00007ffa`91217974 postgres!pg_check_dir+0x68c
0000004e`65fff990 00007ffa`9c84a2f1 KERNEL32!BaseThreadInitThunk+0x14
0000004e`65fff9c0 00000000`00000000 ntdll!RtlUserThreadStart+0x21
2022-05-23 09:10:16.466 GMT [5404][postmaster] LOG: server process (PID 1132) was terminated by exception 0xC0000354
--
Justin
view thread (11+ messages) latest in thread
Message-ID: <20220526032612.GW19626@telsasoft.com>
Permalink: ../20220526032612.GW19626@telsasoft.com/
Also on: postgresql.org/message-id/20220526032612.GW19626@telsasoft.com
copy link · copy postgr.es
reply 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-hackers@postgresql.org
Cc: pryzby@telsasoft.com, andres@anarazel.de, tgl@sss.pgh.pa.us, robertmhaas@gmail.com, andrew@dunslane.net, thomas.munro@gmail.com, melanieplageman@gmail.com, peter.eisentraut@enterprisedb.com, daniel@yesql.se
Subject: Re: ccache, MSVC, and meson
In-Reply-To: <20220526032612.GW19626@telsasoft.com>
* 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