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 1r5uZu-00FroJ-RV for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Nov 2023 21:16:10 +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 1r5uZt-00CqGS-7U for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Nov 2023 21:16:09 +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 1r5uZs-00CqGD-UD for pgsql-hackers@lists.postgresql.org; Wed, 22 Nov 2023 21:16:08 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r5uZq-006rpa-2t for pgsql-hackers@postgresql.org; Wed, 22 Nov 2023 21:16:07 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2023062407; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=MziKmNZagL0RHR0m7n2UFTG3mNqpXsmzTl1YtO0nges=; b=hbaEi blga6UB5OzLivpxAZrSJZ3s5W6ygcVOjn5LQoAZY0SZ8UlSYI+IjqBHdscKnwz9Kf0lU0YbxpiYSC OpqbDbtmLG+WIWqj++uTysfXtEM8vNmxThZe2rHKh9cmeK6kDvJWKDZ7/oJNWw6Z439XwWXeSotbK rD7ApBmDKlgKOEac7zGuK0cDeNzaOdpY6/oDj/otFfNs/k2JuoXa8m7GpziF3bUYrLbVGhfSe8QwF sdWUMcHl/97wXVIRz8fRtL6DwRFYgXovR3HuFswoU0riuC9V1KKb+crjGSOdOyKXvtrNUZ7IW2z60 ZlBmyM2jRm7QN4tHBa85iy7VWBCzA==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1r5uZm-00BFLF-0U; Wed, 22 Nov 2023 16:16:02 -0500 Date: Wed, 22 Nov 2023 16:16:02 -0500 From: Bruce Momjian To: "Fujii.Yuki@df.MitsubishiElectric.co.jp" Cc: Alexander Pyhalov , Robert Haas , PostgreSQL-development , "Finnerty, Jim" , Andres Freund , Tom Lane , Tomas Vondra , Julien Rouhaud , Daniel Gustafsson Subject: Re: Partial aggregates pushdown Message-ID: References: <8175ddeb6d417d8a1f91e667fef77abf@postgrespro.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Nov 22, 2023 at 10:16:16AM +0000, Fujii.Yuki@df.MitsubishiElectric.co.jp wrote: > 2. Approach 2 > (1) Advantages > (a) No need to add partial aggregate functions to the catalogs for each aggregation > (2) Disadvantages > (a) Need to add non-standard keywords to the SQL syntax. > > I did not choose Approach2 because I was not confident that the disadvantage mentioned in 2.(2)(a) > would be accepted by the PostgreSQL development community. > If it is accepted, I think Approach 2 is smarter. > Could you please provide your opinion on which > approach is preferable after comparing these two approaches? I didn't know #2 was possible, but given the great number of catalog entries, doing it in the SQL grammar seems cleaner to me. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.