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 1wqCBB-0024t5-2g for pgsql-hackers@arkaria.postgresql.org; Sat, 01 Aug 2026 16:03:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wqCBA-001Odb-04 for pgsql-hackers@arkaria.postgresql.org; Sat, 01 Aug 2026 16:03:16 +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 1wqC86-001Kyo-0E for pgsql-hackers@lists.postgresql.org; Sat, 01 Aug 2026 16:00:06 +0000 Received: from mail-wr1-x429.google.com ([2a00:1450:4864:20::429]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1wqC84-00000001QbH-12Lk for pgsql-hackers@postgresql.org; Sat, 01 Aug 2026 16:00:05 +0000 Received: by mail-wr1-x429.google.com with SMTP id ffacd0b85a97d-476a130c138so2381951f8f.0 for ; Sat, 01 Aug 2026 09:00:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1785600003; x=1786204803; darn=postgresql.org; h=content-transfer-encoding:content-type:to:subject:from :content-language:user-agent:mime-version:date:message-id:from:to:cc :subject:date:message-id:reply-to:content-type; bh=insZUAM0hW83/FCOyWlIQECgv8OM2w8aQwDIrkrJNdM=; b=s4maE8aH/IozgzzyPMs2JERr+9OUEudtH/AnQEvnwcfN+uwUyubZD9/4p2bo0jzMcN AnMKSF+nEMG/Th5S+cB/1dtViCqu0yRPGYl/mNQpjrCK/a19n/om7e3/rr0nrbErKFqU qvddTbpK4y694wUa0Iy7lDUtUoJIUl1FjyLPKMy0FY9xU4tba3OT8nbP5oRX7Fn25/Uh D6be/x71ixImBgI1bzb+Hp4UUcX6+A0//m654aq/fIdh/cmY5PuO3sC6UbzHZNm+UPus OAjxIkZzjyO3RtumddvwTXVzE76hdL+h+Mrjgm+fukB0+33408aA1Wae50Ibvw9sbH1t /+hg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1785600003; x=1786204803; h=content-transfer-encoding:content-type:to:subject:from :content-language:user-agent:mime-version:date:message-id:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=insZUAM0hW83/FCOyWlIQECgv8OM2w8aQwDIrkrJNdM=; b=LlGyA0y+eEEILYRznSCL62JZXLsbq9Nno8mr6ZWLyOGpREHES7ejPfwYNerqevrouk uk6/96iFxAGhLil69J55ISX1gzwJYg7kPjZvbdoVcxO9eEqMO9nMX3v+cIcxJIv3zwDy i1JJwT2/UKh/Csh+0mSKlSm3Hf4t78iP1AK70Arv2iELInK3JIplPCXwvMk3tLaAS0BZ EvcP5D+9jZBgz/TdWe+XOb2mFh+2b3cxbeDO9MQ63MSnXBjyiLdVHD1niCDTa/Cum+FV kZStBGmHR/LFWiSsWhFNA2B1K8OWGKyX2rd1NQcAzlQskT2zj/3IvSEoPuCxtlIrJOkh k19Q== X-Gm-Message-State: AOJu0YxvJn+QodT8VFuv4fqd8ueIs4y14pRQJHqVPzMQiGySST6DebHM 26GYGazMjeigYunBJKZ8wxEQ+IYiO9gemQIBmE6FF7SIdDUmPYGOmQaAUnvThA== X-Gm-Gg: AR+sD13SLRIiB33CMElzdeBU/1bwbMxLfqYzpe/xlwy9w4c2BzkhNnzUnAkkY/g5YO1 xGX2xroPBdbF7Gcb64qouEpiPoBdSylrGSXwfSrLA5TlCKesESqQ0WZR6QAMYaVv4APar6Grkt/ 7r6KXg1+W9V938xExZf9PQbhTMVLEjXSFT/F4duOEbWdLLDwTFHZY3RO0pdRnLZJUxf0hY50nPj qV6HG6eXZwJRHRmXCEfkT+z1eaL2bGBCDqwkMWpwOJowhIIfCtJA25BJkG8VGHYW+qLQwJ85Rbe WOxjV1ozEDRGpqzrH/iY1cMcVSJ67lAj/saccSsp36ESN+P5YcNJJ0wbzVNvA5zSv16WlV/xOdN rj5dYTC2gJuEyOEbrcdDvE6SoZSDEueNpxfHgBUhVQ7t5rsSxFxGgzkMBDoCt+eWYJF4awdm8Mj sdEng3ayb1N5x6V5al/1MzgHRFN+gdtwQxHvtTYsUYIOWPkqCweo+2IpspIM6fnEc= X-Received: by 2002:a05:6000:25f3:b0:46e:1815:6a83 with SMTP id ffacd0b85a97d-47fd72f1666mr8909472f8f.29.1785600002507; Sat, 01 Aug 2026 09:00:02 -0700 (PDT) Received: from [192.168.0.50] ([89.149.120.180]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-47fd41e2961sm18751960f8f.13.2026.08.01.09.00.01 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 01 Aug 2026 09:00:01 -0700 (PDT) Message-ID: <7a68bee2-91bd-481d-be44-160e6beebc83@gmail.com> Date: Sat, 1 Aug 2026 19:00:00 +0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US From: Alexander Lakhin Subject: xid_wraparound/002_limits.pl might fail due to transient warning To: pgsql-hackers Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello hackers, New buildfarm animal partridge (aarch64, maybe with slow storage) produced several unprecedented failures of 002_limits, e.g., [1], [2]: 389/400 xid_wraparound - postgresql:xid_wraparound/002_limits ERROR           601.34s   exit status 1 [01:32:22.020](6.936s) not ok 3 [01:32:22.023](0.003s) #   Failed test at /home/buildfarm/pg-buildfarm/builds/HEAD/pgsql/src/test/modules/xid_wraparound/t/002_limits.pl line 130. [01:32:22.024](0.001s) #          got: 'start # oldxact # after 1 billion # after 2 billion # reached warn-limit # after VACUUM # after VACUUM' #     expected: 'start # oldxact # after 1 billion # after 2 billion # reached warn-limit # after VACUUM' That is: # Wait until autovacuum has processed the other databases and advanced # the system-wide oldest-XID. $ret =   $node->poll_query_until('postgres',     qq[INSERT INTO wraparoundtest VALUES ('after VACUUM')],     'INSERT 0 1'); has been successfully executed two times instead of one. 002_limits_wraparound.log contains: 2026-07-24 01:32:21.791 UTC client backend[3424568] 002_limits.pl LOG:  statement: INSERT INTO wraparoundtest VALUES ('after VACUUM') 2026-07-24 01:32:21.793 UTC client backend[3424568] 002_limits.pl WARNING:  database "template0" must be vacuumed within 87544676 transactions 2026-07-24 01:32:21.793 UTC client backend[3424568] 002_limits.pl DETAIL:  Approximately 4.08% of transaction IDs are available for use. 2026-07-24 01:32:21.793 UTC client backend[3424568] 002_limits.pl HINT:  To avoid transaction ID assignment failures, execute a database-wide VACUUM in that database.     You might also need to commit or roll back old prepared transactions, or drop stale replication slots. 2026-07-24 01:32:21.947 UTC client backend[3424573] 002_limits.pl LOG:  statement: INSERT INTO wraparoundtest VALUES ('after VACUUM') First INSERT succeeded, but with the WARNING, which didn't satisfy poll_query_until(). I've reproduced similar failures with extra autovacuum/vacuum settings, but the reproducer is still too timing-dependent to share, so maybe this illustration will do: --- a/src/test/modules/xid_wraparound/t/002_limits.pl +++ b/src/test/modules/xid_wraparound/t/002_limits.pl @@ -95,6 +95,10 @@ is($warn_limit, 1, "warn-limit reached");  # We can still INSERT, despite the warnings.  $node->safe_psql('postgres',      qq[INSERT INTO wraparoundtest VALUES ('reached warn-limit')]); +$ret = +  $node->poll_query_until('postgres', +    qq[INSERT INTO wraparoundtest VALUES ('reached warn-limit')], +    'INSERT 0 1'); PROVE_TESTS="t/002*" PG_TEST_EXTRA="xid_wraparound" PG_TEST_TIMEOUT_DEFAULT=5 make -s check -C src/test/modules/xid_wraparound/ gives: t/002_limits.pl .. 1/? # poll_query_until timed out executing this query: # INSERT INTO wraparoundtest VALUES ('reached warn-limit') # expecting this output: # INSERT 0 1 # last actual query output: # INSERT 0 1 # with stderr: # WARNING:  database "postgres" must be vacuumed within 97483575 transactions # DETAIL:  Approximately 4.54% of transaction IDs are available for use. # HINT:  To avoid transaction ID assignment failures, execute a database-wide VACUUM in that database. # You might also need to commit or roll back old prepared transactions, or drop stale replication slots. Probably this can be fixed with (it works for my repro): $ret =   $node->poll_query_until('postgres',     qq[SET client_min_messages='ERROR'; INSERT INTO wraparoundtest VALUES ('after VACUUM')],     "SET\nINSERT 0 1"); [1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=partridge&dt=2026-07-22%2011%3A37%3A59 [2] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=partridge&dt=2026-07-24%2000%3A00%3A42 Best regards, Alexander