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.94.2) (envelope-from ) id 1r0JoX-004xoJ-4I for pgsql-hackers@arkaria.postgresql.org; Tue, 07 Nov 2023 11:00:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1r0JoV-007RK4-H3 for pgsql-hackers@arkaria.postgresql.org; Tue, 07 Nov 2023 11:00:07 +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.94.2) (envelope-from ) id 1r0JoV-007RJv-7k for pgsql-hackers@lists.postgresql.org; Tue, 07 Nov 2023 11:00:07 +0000 Received: from mail-lf1-x132.google.com ([2a00:1450:4864:20::132]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1r0JoS-004O4P-S2 for pgsql-hackers@lists.postgresql.org; Tue, 07 Nov 2023 11:00:06 +0000 Received: by mail-lf1-x132.google.com with SMTP id 2adb3069b0e04-507a5f2193bso5937800e87.1 for ; Tue, 07 Nov 2023 03:00:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699354803; x=1699959603; darn=lists.postgresql.org; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=98yHy9lkuZnBl/KDUDGZULyfOYp2M8iWjK6Z1kgsDrM=; b=GGcbLDa0axH8KUmXwrwYJDWoGj9yZ1ytU89rSGKyB0Glrsz5FIJdpd+YWb7DRnADO3 L1KHQmlC/DChga3AqWlDcxmTNKJsYkZhsMBhNOmXW+zJo0NNGToHhQeP9VpugEYMW1HW 3+BVQhWEBWh2eFGAt1ZiyfEzya/8buwQLzChRjbCfZ7New23a6rdBYBGGJFetlG0A1QQ 2a6yB6NusezkYPyGctOcgUl63+iPeLts9XHLlpnrnJRRT/fuuPr487vTV2aaSx8Ct9sa 1jlgo4EkWmEx/0PU3gM1q03oxvTBmwg4H+59RLr+02v6yl7QGDcS2jncZBtc8Fm9r+fA 0LOQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699354803; x=1699959603; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=98yHy9lkuZnBl/KDUDGZULyfOYp2M8iWjK6Z1kgsDrM=; b=bTORjmZwktsDG9DG5pZTjHHrzTh1bhfF3CkrNk3Hn1kxNfQuKnXW1MDQtaWRcXev6u LUOLGyzUKZsInT0ZWN+SOZgxFxcc+CITsCZDv56z2rcejSGbPauJ1CR980D4ctpjIE4M RmkMXhZMv/qGPh+SIGr6eru1IQC7w+PhDbMl+cN1O97te6u1vWTk4tocjeRFu7Pnjvhc H0BbfpjQ1JZvFgyc1DBEEv9Z70x6da2hekh9gEsi5CT6YmGRgDIWDd7FMrYdP7HSwwb8 afzdvYkDDYMQRto+ZW0VFoakUwwEFJPy0nhDUOYlZ5+QbXN+V0zuZ7gzunGEonb0IiZq P1Fg== X-Gm-Message-State: AOJu0Yxz6Pwwzhkd/nLZSwEJE0TjXXvZjCsuwqMXL6n6kt62G9HcbRpi mbtBlThH6RV9T8Yin7e0cyo= X-Google-Smtp-Source: AGHT+IFiKj5Sqzo1e97jSq4Cx7d0tbFbotxIcmfv2GTA2/KhwG1KgJ1tzchxCJ2gnw5C5VW9Z7EXmg== X-Received: by 2002:a05:6512:ac9:b0:509:366b:a01c with SMTP id n9-20020a0565120ac900b00509366ba01cmr927473lfu.14.1699354803043; Tue, 07 Nov 2023 03:00:03 -0800 (PST) Received: from [1.0.0.7] ([178.155.28.40]) by smtp.gmail.com with ESMTPSA id j21-20020ac24555000000b00504816564c7sm315454lfm.104.2023.11.07.03.00.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 07 Nov 2023 03:00:02 -0800 (PST) Message-ID: Date: Tue, 7 Nov 2023 14:00:00 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: collect_corrupt_items_vacuum.patch Content-Language: en-US To: Alexander Korotkov , Daniel Gustafsson Cc: Daniel Shelepanov , Nikita Malakhov , Michael Paquier , Robert Haas , Tom Lane , PostgreSQL Hackers , Andres Freund References: <1649062270.289865713@f403.i.mail.ru> <3107109.1658958956@sss.pgh.pa.us> From: Alexander Lakhin In-Reply-To: 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 Hi Alexander, 06.11.2023 12:30, Alexander Korotkov wrote: > Surely these would significantly sacrifice accuracy. But we have to do > so in order to avoid reporting false errors. > I've reduced the dirty reproducer Daniel Shelepanov posted initially to the following: numdbs=10 for ((d=1;d<=$numdbs;d++)); do   createdb db$d   psql db$d -c "create extension pg_visibility" done for ((i=1;i<=300;i++)); do echo "iteration $i" for ((d=1;d<=$numdbs;d++)); do ( echo " create table vacuum_test as select 42 i; vacuum (disable_page_skipping) vacuum_test; select * from pg_check_visible('vacuum_test'); " | psql db$d -a -q >psql-$d.log 2>&1 ) & done wait res=0 for ((d=1;d<=$numdbs;d++)); do grep -q '0 rows' psql-$d.log || { echo "Error condition in psql-$d.log:"; cat psql-$d.log; res=1; break; } psql db$d -q -c "drop table vacuum_test" done [ $res == 0 ] || break; done It looks like the v2 patch doesn't fix the original issue. Maybe I miss something, but with the patch applied, I see the failure immediately, though without the patch several iterations are needed to get it. Best regards, Alexander