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 1kKkbv-0006TG-PO for pgsql-bugs@arkaria.postgresql.org; Tue, 22 Sep 2020 15:53:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kKkbs-0005nW-TW for pgsql-bugs@arkaria.postgresql.org; Tue, 22 Sep 2020 15:53:40 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kKkbs-0005l3-NQ for pgsql-bugs@lists.postgresql.org; Tue, 22 Sep 2020 15:53:40 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kKkbq-0005jM-PY for pgsql-bugs@lists.postgresql.org; Tue, 22 Sep 2020 15:53:39 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 08MFrbLv1247745; Tue, 22 Sep 2020 11:53:37 -0400 From: Tom Lane To: kanaga@consumeracquisition.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16627: union all with partioned table yields random aggregate results In-reply-to: <16627-1a2233d31af8d35b@postgresql.org> References: <16627-1a2233d31af8d35b@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Tue, 22 Sep 2020 15:10:51 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1247743.1600790017.1@sss.pgh.pa.us> Date: Tue, 22 Sep 2020 11:53:37 -0400 Message-ID: <1247744.1600790017@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > The following bug has been logged on the website: > Bug reference: 16627 > Logged by: Brian Kanaga > Email address: kanaga@consumeracquisition.com > PostgreSQL version: 11.4 > Operating system: Linux > Description: > Hoping this is something already discovered as the amount of data to > recreate is cumbersome. Well, 11.4 is more than a year out of date. Can you still reproduce this on the current minor release (11.9)? regards, tom lane