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 1ppBQ2-0002Aa-J6 for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Apr 2023 17:16:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ppBQ1-0004J9-Ew for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Apr 2023 17:16:33 +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 1ppBQ1-0004J0-1x for pgsql-hackers@lists.postgresql.org; Wed, 19 Apr 2023 17:16:33 +0000 Received: from mail-il1-x133.google.com ([2607:f8b0:4864:20::133]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1ppBPw-003rpG-DB for pgsql-hackers@postgresql.org; Wed, 19 Apr 2023 17:16:32 +0000 Received: by mail-il1-x133.google.com with SMTP id e9e14a558f8ab-32adf94ac1bso6454525ab.0 for ; Wed, 19 Apr 2023 10:16:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20221208.gappssmtp.com; s=20221208; t=1681924586; x=1684516586; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=LlCJjIkCYtdRbbJhwU4LXKioYlsju0MMOI1huNEVhoo=; b=YqcyrNaC2s2VupvXuqjrWJFNH3Wz38eb6UT/8e+tdiC30si6meIYvXOxQHlcWRAa+a 1Z3GJy92uehXx5IJTiJLtrVz4npoC1M4fU901U9eemdKDIxylymJ1+f0YTMf5fRr6jrW vahgF+A2uMUkiYAMlVEHbdrG5x1NFbwUTMsQGbTPHsaCUUfv7YztyyKqNatHKwfdB50X Loqh0UmC1kYRgRFUlOhl1bbcXD05WuOzqBHFYmrqofvRVEdcLXbUt+EHPyvmd+WBWYy2 5NrMmofHicI7b8/VJz6Lvc0F4+S2e7OWZ+MvXS2D1Fj4b5ZNn4d1YJHVyZHp7La9OLm9 UfKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681924586; x=1684516586; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=LlCJjIkCYtdRbbJhwU4LXKioYlsju0MMOI1huNEVhoo=; b=O29jVtxGgS5MBB3a5ucTyC644aRHrBlBvIhDQJdMOXFGP+qwYggfCpYHWhSNv7QxLt Bx1NEeRSMZT0fdYnXh8Z9eavoPy/2es7M5czDZrDDg8izx4/YAT6IIPRRsBpB1SukO6P wo+RLuBXU5cSOc9b0sYNMXoK9FdbijxFBlHy89s0wCF+sOpGWwbkRSti7uTvb2lV8VEC wrpQtuDVb7ausjahDzSouy9C5266x8xNQsQ/avRWUqftTvq3iMNHHsPSPpZi/VUoEKn1 g8l6yjmw8mACvkcCSiLhQQyoqS7om7B5WJWHS6H02ii9iYP0Sg/q/J8AL8KXRH3yRRlx s3zg== X-Gm-Message-State: AAQBX9ctNrs2AwLvpwxT9KEnfLQIEuX/TEAusmwpxhxHaFLNGvwGj1cN Dc6la/tr5zFHzDJg8JaoHusH9A== X-Google-Smtp-Source: AKy350bhj4oGIIpdzeUQhy14sxE4wsZgTDWaR95NifXvhxwvFuwkCpUYXHTYOZuOV2uqYoYSNjvc6g== X-Received: by 2002:a92:c68f:0:b0:326:17e2:bc99 with SMTP id o15-20020a92c68f000000b0032617e2bc99mr454412ilg.28.1681924586469; Wed, 19 Apr 2023 10:16:26 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id bw14-20020a056638460e00b0040fbd94b0adsm1108078jab.67.2023.04.19.10.16.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 19 Apr 2023 10:16:25 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id C8C8A800DAF; Wed, 19 Apr 2023 12:16:24 -0500 (CDT) Date: Wed, 19 Apr 2023 12:16:24 -0500 From: Justin Pryzby To: Melanie Plageman Cc: Thomas Munro , Andres Freund , Richard Guo , pgsql-hackers@postgresql.org Subject: Re: Wrong results from Parallel Hash Full Join Message-ID: References: <20230412181452.cyfduw2ka2atqmii@awork3.anarazel.de> <20230419151704.xkkobswffutslj34@liskov> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230419151704.xkkobswffutslj34@liskov> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Apr 19, 2023 at 11:17:04AM -0400, Melanie Plageman wrote: > Ultimately this is probably fine. If we wanted to modify one of the > existing tests to cover the multi-batch case, changing the select > count(*) to a select * would do the trick. I imagine we wouldn't want to > do this because of the excessive output this would produce. I wondered > if there was a pattern in the tests for getting around this. You could use explain (ANALYZE). But the output is machine-dependant in various ways (which is why the tests use "explain analyze so rarely). So you'd have to filter its output with a function (like the functions that exist in a few places for similar purpose). -- Justin