Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1weYSr-004rmo-2J for pgsql-bugs@arkaria.postgresql.org; Tue, 30 Jun 2026 13:25:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1weYSq-008KaV-1Z for pgsql-bugs@arkaria.postgresql.org; Tue, 30 Jun 2026 13:25:24 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1weT1n-0070GJ-38 for pgsql-bugs@lists.postgresql.org; Tue, 30 Jun 2026 07:37:08 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1weT1l-00000000spg-2K7c for pgsql-bugs@lists.postgresql.org; Tue, 30 Jun 2026 07:37:07 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=eIU9bsmvkKVNHVrcoC2YDTYBFToezBmbE9T3GlISgx0=; b=x22CFv/B1cx6pBp2nmC72gF3Mb EgVv0UO0QDPozH3/f8PiHPz74dpqgASTwQnhIvP3I5W661UvN4QwSckr+3b7/A8AyajjlNwMUP2Tk 4R6OCFq+gXjqphKUOZEgJP3+nW3OtoiymV2MEv+qZ6D4yBNRW53aVSvWQ+FhIjlEGeMGDpHInZxv4 kUxWnoJ0zHY5QDLOv+tyDZMjRO2ITCaJ8KyyP5LV8NZ1GVrk344AsXls3hSEMKHvMlQrHQnHb9tnN P82uKBESt33vBN7G5WoktHi2mpU1N64ZLV505GgKPiQMAkRhz2HnM06GmJmt8SIM9l8LitEORFOnj VfsL4rUw==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1weT1l-008dYZ-0L for pgsql-bugs@lists.postgresql.org; Tue, 30 Jun 2026 07:37:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1weT1j-006bcP-2B for pgsql-bugs@lists.postgresql.org; Tue, 30 Jun 2026 07:37:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: BUG #19541: Postgresql failed to run 150+ tests on both debug and release configurations with VS 2026 on Windows To: pgsql-bugs@lists.postgresql.org From: PG Bug reporting form Cc: karenhuang2017@gmail.com Reply-To: karenhuang2017@gmail.com, pgsql-bugs@lists.postgresql.org Date: Tue, 30 Jun 2026 07:37:00 +0000 Message-ID: <19541-059eb8da45044c7c@postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following bug has been logged on the website: Bug reference: 19541 Logged by: Karen Huang Email address: karenhuang2017@gmail.com PostgreSQL version: 19beta1 Operating system: Windows 11 Description: =20 The MSVC team regularly builds popular open-source projects, including yours, with development versions of the build tools in order to find and fix regressions in the compiler and libraries before they can ship and cause trouble for the world. This also allows us to provide advance notice of breaking changes, which is the case here. We build Postgresql with VS 2026 on Windows. It failed to run 150+ tests on both debug and release configurations. Could you please help to take a look? Thanks in advance! Repro steps: 1. git clone https://git.postgresql.org/git/postgresql.git C:\gitP\postgres\postgres 2. C:\tools\msys64\usr\bin\pacman --noconfirm -S flex bison diffutils 3. Open VS 2026 x64 CMD. 4. cd /d C:\gitP\postgres\postgres 5. mkdir build_amd64 && cd build_amd64 6. set PATH=3D%PATH%;C:\tools\msys64\usr\bin 7. pip3 install meson 8. meson setup --buildtype release 9. ninja -v 10. meson test --no-suite libpq_pipeline Test result: The error log is quite large, so it's not practical to paste it into the email. It also appears that we can't attach log files to this thread. Could you please advise on the preferred way to share the complete log? We can upload it to a file-sharing service or use any other method you recommend. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 7/383 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D test: recovery - postgresql:recovery/001_stream_rep start time: 02:28:46 duration: 84.25s result: exit status 9 command: top_builddir=3DC:\gitP\postgres\postgres\build_amd64 enable_injection_points=3Dno MSAN_OPTIONS=3Dhalt_on_error=3D1:abort_on_error=3D1:print_summary=3D1:print= _stacktrace=3D1 UBSAN_OPTIONS=3Dhalt_on_error=3D1:abort_on_error=3D1:print_summary=3D1:prin= t_stacktrace=3D1 MALLOC_PERTURB_=3D88 share_contrib_dir=3DC:/gitP/postgres/postgres/build_amd64/tmp_install//usr/= local/pgsql/share/contrib PG_REGRESS=3DC:\gitP\postgres\postgres\build_amd64\src/test\regress\pg_regr= ess.exe INITDB_TEMPLATE=3DC:/gitP/postgres/postgres/build_amd64/tmp_install/initdb-= template REGRESS_SHLIB=3DC:\gitP\postgres\postgres\build_amd64\src/test\regress\regr= ess.dll MESON_TEST_ITERATION=3D1 ASAN_OPTIONS=3Dhalt_on_error=3D1:abort_on_error=3D1:print_summary=3D1 C:\Python312\python.EXE C:\gitP\postgres\postgres\build_amd64\..\src/tools/testwrap --basedir C:\gitP\postgres\postgres\build_amd64 --srcdir C:\gitP\postgres\postgres\src/test\recovery --pg-test-extra --testgroup recovery --testname 001_stream_rep -- C:\Strawberry\perl\bin\perl.EXE -I C:/gitP/postgres/postgres/src/test/perl -I C:\gitP\postgres\postgres\src/test\recovery C:/gitP/postgres/postgres/src/test/recovery/t/001_stream_rep.pl ----------------------------------- stdout ----------------------------------- # executing test in C:\gitP\postgres\postgres\build_amd64/testrun/recovery/001_stream_rep group recovery test 001_stream_rep # initializing database system by copying initdb template 1..0 # test failed ----------------------------------- stderr ----------------------------------- # die: WAIT FOR LSN failed: error running SQL: 'psql::1: ERROR: invalid input syntax for type pg_lsn: "0/03045AA0 " ' # while running 'psql --no-psqlrc --no-align --tuples-only --quiet --dbname port=3D30741 host=3D127.0.0.1 dbname=3D'postgres' --file - --variable ON_ERROR_STOP=3D1' with sql 'WAIT FOR LSN '0/03045AA0 ' WITH (MODE 'standby_replay', timeout '180s', no_throw);' at C:/gitP/postgres/postgres/src/test/recovery/t/001_stream_rep.pl line 72. # at C:/gitP/postgres/postgres/src/test/recovery/t/001_stream_rep.pl line 72. (test program exited with status code 9) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D .... Ok: 174 Fail: 154 Skipped: 46 Timeout: 8 Thanks, Karen