From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Finnerty, Jim <jfinnert@amazon.com>
Cc: Japin Li <japinli@hotmail.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: pgsql-hackers@lists.postgresql.org <pgsql-hackers@lists.postgresql.org>
Subject: Re: parse partition strategy string in gram.y
Date: Mon, 24 Oct 2022 18:13:17 +0200
Message-ID: <20221024161317.3ywktkv2ghqpp4as@alvherre.pgsql> (raw)
In-Reply-To: <03B39DA5-53BB-4E8D-82D9-C5C601DB8F6E@amazon.com>
On 2022-Oct-24, Finnerty, Jim wrote:
> Is there a reason why HASH partitioning does not currently support
> range partition bounds, where the values in the partition bounds would
> refer to the hashed value?
Just lack of an implementation, I suppose.
> The advantage of hash partition bounds is that they are not
> domain-specific, as they are for ordinary RANGE partitions, but they
> are more flexible than MODULUS/REMAINDER partition bounds.
Well, modulus/remainder is what we have. If you have ideas for a
different implementation, let's hear them. I suppose we would have to
know about both the user interface and how it would internally, from two
perspectives: how does tuple routing work (ie. how to match a tuple's
values to a set of bound values), and how does partition pruning work
(ie. how do partition bounds match a query's restriction clauses).
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@alvh.no-ip.org, jfinnert@amazon.com, japinli@hotmail.com, pryzby@telsasoft.com, pgsql-hackers@lists.postgresql.org
Subject: Re: parse partition strategy string in gram.y
In-Reply-To: <20221024161317.3ywktkv2ghqpp4as@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox