Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qBkyD-0004Ca-Mg for pgsql-bugs@arkaria.postgresql.org; Tue, 20 Jun 2023 23:41:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qBkyC-0003ti-9Q for pgsql-bugs@arkaria.postgresql.org; Tue, 20 Jun 2023 23:41:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qBkyC-0003tY-0J for pgsql-bugs@lists.postgresql.org; Tue, 20 Jun 2023 23:41:08 +0000 Received: from mail-wm1-x32c.google.com ([2a00:1450:4864:20::32c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qBky4-003iCY-3g for pgsql-bugs@lists.postgresql.org; Tue, 20 Jun 2023 23:41:06 +0000 Received: by mail-wm1-x32c.google.com with SMTP id 5b1f17b1804b1-3f9189228bcso28716635e9.3 for ; Tue, 20 Jun 2023 16:40:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1687304458; x=1689896458; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=wjgAIi+CFNkU0XPJiKkKJscDzMhIry5DzbCH/+Km8Xg=; b=YeZ+jqFN6ZsuiZy8AU0aCGmmtNAaWoFhq1h/YdYi2ZDTqP9bDERN51tH4oNjB7LkJq RQo39Xp7zbI5IshnIOnVBSsHLBG/6KKRdfJLW9blDo0Bou0CvXXK2SdKglxsHzQmbice Iri1nzf2Bwg7OOOIU0BzSrQNjxF7WCAnnU6jMDaUGhoiSDYfENQTobAROswRxId6vaJj xpQtMK4ldmfFzY0JFcf6PYBRVqXKVnKErd5oZBneJ/LSKVT+S12RwALbcADhbyYnMkZG Zj6COm0p6OSHBD2NnmuDqfTO/im3jWqiEkl2ZGTA/F3pz3xWsGtzEmOekZFkj2b5AhYJ tpDQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687304458; x=1689896458; h=content-transfer-encoding:in-reply-to:from:references: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=wjgAIi+CFNkU0XPJiKkKJscDzMhIry5DzbCH/+Km8Xg=; b=e9w5cYe2RFUE2VxBhjYez0FGkL7n8Wkrjw9ppMBHx2rfVdSoEM6/aE8DqDBsMGLK/s tPKhy905/XKJxmaxZoxaaDAObtneN6yhleo9g9C92CLAhFQAAJ/zfz2TAQ+y7O17EwBH luxthy0V3g7zfov5Um1cmqq8mw6gF8Ztumzt5UHDfRTXCtrh5EQBwqoF8BytBIiQP81c +ZjQ3XJFGGZo2N89DCt0N5r60nAMBowTKNF4EhSJdePImgz91BZAqKzWceo9vIAwQDwF bVFIh/rhlR8MW+1OI/wCU9FM5Lm2G0Di6NxaAt8r9Iim2e6LEWPgj2ap6tTDgfuq0aBH JjwA== X-Gm-Message-State: AC+VfDwZJ/IKc65yw4M76B6CtyFsPs+68ZaneoewSLZLRM8Lyhxvupc4 NJbKljKzqvAI89RCo4yAi2DbFw== X-Google-Smtp-Source: ACHHUZ7rZwDf3OW0oaRB+qlSQc/0YreuacvXpwKue4qUb+rfPp8/j/RRaRdVYEXEz27z+Yk5Ert2Cg== X-Received: by 2002:a5d:4a51:0:b0:309:419b:925d with SMTP id v17-20020a5d4a51000000b00309419b925dmr9264781wrs.70.1687304458280; Tue, 20 Jun 2023 16:40:58 -0700 (PDT) Received: from [10.137.0.17] (ip-86-49-228-220.bb.vodafone.cz. [86.49.228.220]) by smtp.gmail.com with ESMTPSA id e10-20020a5d65ca000000b002f28de9f73bsm3002164wrw.55.2023.06.20.16.40.57 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 20 Jun 2023 16:40:57 -0700 (PDT) Message-ID: Date: Wed, 21 Jun 2023 01:40:56 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.1 Subject: Re: BUG #17986: Inconsistent results of SELECT affected by btree index Content-Language: en-US To: zuming.jiang@inf.ethz.ch, pgsql-bugs@lists.postgresql.org, PG Bug reporting form References: <17986-6ebf8b5d2c3a4f6e@postgresql.org> From: Tomas Vondra In-Reply-To: <17986-6ebf8b5d2c3a4f6e@postgresql.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 6/20/23 22:54, PG Bug reporting form wrote: > The following bug has been logged on the website: > > Bug reference: 17986 > Logged by: Zuming Jiang > Email address: zuming.jiang@inf.ethz.ch > PostgreSQL version: 16beta1 > Operating system: Ubuntu 20.04 > Description: > > My fuzzer finds a correctness bug in Postgres, which makes Postgres return > inconsistent results. This bug can be reproduced even after applying the > fixing patches for > https://www.postgresql.org/message-id/flat/17976-4b638b525e9a983b%40postgresql.org > > https://www.postgresql.org/message-id/flat/17982-3fa239feecd6c1b3%40postgresql.org > https://www.postgresql.org/message-id/flat/17985-748b66607acd432e%40postgresql.org > > ... > > --- Postgres version --- > Github commit: efeb12ef0bfef0b5aa966a56bb4dbb1f936bda0c > Version: PostgreSQL 16beta1 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu > 9.4.0-1ubuntu1~20.04.1) 9.4.0, 64-bit > I can't reproduce this with current master - perhaps one of the commits since efeb12ef0b fixes this too? Those should be for the patches you mentioned, but it's likely a bit improved. Can you try with current master? regards -- Tomas Vondra EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company